Hi Sapna, The bad news is that there is no workflow action that will accomplish this for you. You could potentially try to use a SQL update (in a Direct SQL action) to directly update the Remedy data dictionary, which would look something like this:
UPDATE escalation SET enable = 0 WHERE name = 'The Escalation Name' But I'd recommend against this for two reasons. First, any running AR servers would not notice the change until they reload their data dictionary caches. Second, doing this *might* cause the escalation to become invalid in that it would no longer match the checksum (in the safeGuard column of the escalation table). I haven't checked this and don't know offhand if the "enable" is part of that checksum. The only way I can think of would be to write a small API program that performs the action. This would immediately affect the AR server on which it's run, but it would not propagate to any other servers until they reload their caches (I don't know much about server groups...would other servers in the group notice such changes and automatically reload?). I hope this helps. -charlie On Wed, Apr 30, 2014 at 12:06 PM, Sapna Motwani <[email protected]>wrote: > Hello Experts, > > Please suggest is it possible to define a self-terminating escalation. I > need to run an escalation just once, and then it should disable itself. > I want to know is it possible to define an escalation which triggers some > workflow to mark the calling parent escalation as disable. > > Any help would be highly appreciated. > > Regards, > Sapna > > > _______________________________________________________________________________ > 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"
