Why not use the DSO process for this? Vikrant
Sent from my Xperia™ smartphone Vivek Garg <vivek_ussd...@yahoo.com> wrote: Hi, We are trying to achieve remedy ebonding i.e. bidirectional incidents sync between 2 remedy systems. We have created an AO(Atrium Ochestrator) process which we are trying to consume through set fields action in a filter. Now we want the update/modifications to happen first on remedy 1 and then our filter should call AO process to make the same changes on 2nd remedy.If there is some issue with the AO like CDP is down or for any reason my AO process failed, then we do not want to loose changes made on remedy 1, we want to store these changes in a temporary table and with the help of an esclation we want to resend these changes again through our AO process once it's up. Basically what I want to know is that how should I design such a workflow which ensures that AO process must be called after changes successfully gets stored on Remedy 1. Please suggest some approach to implement this. Thanks , VIvek _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
