OK, good news and bad news…… The best way to do this is to create an escalation that is disabled. Then, tell it to run one time.
Well, that seems to be perfect and just what you asked for. So, how do you do this??? Well, that is the bad news. While we do have the exact functionality, we have not made it easy for you to get to. You can create an escalation and it can be disabled. NO problem there. Now, there is way using an API call to say to run ANY escalation (enabled or disabled) ONE TIME RIGHT NOW. So, this is good news. The bad news is that we have not exposed a way to call that API call from Dev Studio. This means you have to call it from an API program or use the driver sample program we ship to cause it to run. Using driver, you can create a small script that performs the login, runs the escalation, and terminates and pass the escalation name in as a parameter. Then, you could just run that script directly (or through workflow) to perform the operation. A good enhancement request is to have the ability to say to "run now" for an escalation exposed through dev studio. Other than this feature, you have to enable it so that it triggers and runs and then disable it so that it does not run again. There is no other way to manage this. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Charlie Lotridge Sent: Thursday, May 01, 2014 10:18 AM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** 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 <sapana.motw...@gmail.com<mailto:sapana.motw...@gmail.com>> 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<http://www.arslist.org> "Where the Answers Are, and have been for 20 years" _ARSlist: "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"
