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
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
which we want to store in a temporary table and then resend them again
with the help of an escalation.
Regards,
Vivek
--- On Sun, 2/3/13, Kulkarni, Vikrant vkulka...@columnit.com wrote:
From: Kulkarni, Vikrant vkulka...@columnit.com
Subject: Re: Issues with Remedy Ebonding- Consuming AO process
3 matches
Mail list logo