Re: Self-Terminating/disabling Escalation
The “Run Now” escalation option is also there in the 7.5 Dev Studio (at least in patch 007). David D. David Durling University of Georgia From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jarl Grøneng Sent: Tuesday, May 06, 2014 7:21 AM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** This option was added to 7.6.04 Developer Studio. Using 7.6.04 Develper Studio against 7.5 or lower server version will also enable this option. -- J 2014-05-02 20:03 GMT+02:00 Rick Westbrock mailto:rwestbr...@24hourfit.com>>: ** I think that was in place as of version 7.6.04 since I remember right-clicking to run an escalation last year (but maybe my memory is faulty, I don’t have a 7.6.04 system to reference now). -Rick _ Rick Westbrock Remedy Administrator | IT Department 24 Hour Fitness USA, Inc. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of LJ LongWing Sent: Friday, May 02, 2014 9:18 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Self-Terminating/disabling Escalation ** Doug, I hate to contradict you, but, if you right click on any escalation, the bottom option is 'Run Now'so, at least in the 8.1 version of the Dev Studio, there is a GUI option that enables this. On Thu, May 1, 2014 at 1:22 PM, Mueller, Doug mailto:doug_muel...@bmc.com>> wrote: ** 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<mailto:arslist@ARSLIST.ORG>] On Behalf Of Charlie Lotridge Sent: Thursday, May 01, 2014 10:18 AM To: arslist@ARSLIST.ORG<mailto: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 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
Re: Self-Terminating/disabling Escalation
This option was added to 7.6.04 Developer Studio. Using 7.6.04 Develper Studio against 7.5 or lower server version will also enable this option. -- J 2014-05-02 20:03 GMT+02:00 Rick Westbrock : > ** > > I think that was in place as of version 7.6.04 since I remember > right-clicking to run an escalation last year (but maybe my memory is > faulty, I don’t have a 7.6.04 system to reference now). > > > > -Rick > > > > *_* > > *Rick Westbrock* > Remedy Administrator | IT Department > 24 Hour Fitness USA, Inc. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing > *Sent:* Friday, May 02, 2014 9:18 AM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Self-Terminating/disabling Escalation > > > > ** > > Doug, > > I hate to contradict you, but, if you right click on any escalation, the > bottom option is 'Run Now'so, at least in the 8.1 version of the Dev > Studio, there is a GUI option that enables this. > > > > On Thu, May 1, 2014 at 1:22 PM, Mueller, Doug > wrote: > > ** > > 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 > 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. > >
Re: Self-Terminating/disabling Escalation
I think that was in place as of version 7.6.04 since I remember right-clicking to run an escalation last year (but maybe my memory is faulty, I don’t have a 7.6.04 system to reference now). -Rick _ Rick Westbrock Remedy Administrator | IT Department 24 Hour Fitness USA, Inc. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Friday, May 02, 2014 9:18 AM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** Doug, I hate to contradict you, but, if you right click on any escalation, the bottom option is 'Run Now'so, at least in the 8.1 version of the Dev Studio, there is a GUI option that enables this. On Thu, May 1, 2014 at 1:22 PM, Mueller, Doug mailto:doug_muel...@bmc.com>> wrote: ** 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<mailto:arslist@ARSLIST.ORG>] On Behalf Of Charlie Lotridge Sent: Thursday, May 01, 2014 10:18 AM To: arslist@ARSLIST.ORG<mailto: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 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_ _ARSlist: "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"
Re: Self-Terminating/disabling Escalation
LJ, Although it's not a feature that I've found particularly useful, your use case sounds like a perfect candidate for an "error handler" filter. If you use one on the target form (of the push) to catch the individual errors, it should allow the whole transaction to succeed. However, there's another reason the "use a table loop to push to target entries" may not be a good idea...it's not scalable. All of the filters executed in that single run of the escalation's actions count toward the filter limit set for the system. So if the number of target entries might be or grow large, a run of this thing might hit the system limit and abort (and rollback) the entire transaction. If you use the "normal" paradigm and have the escalation running on the target form directly (instead of from a control form), each run of the escalation's actions resets the filter counter, lessening the probability of hitting the limit. -charlie On May 3, 2014 5:48 AM, "LJ LongWing" wrote: > ** > Doug/All, > I'll let you know about a 'problem' I have come across with this approach. > Unfortunately, or fortunately, depending on how you look at it, a Push > action requires that all actions on the push succeed for any to be > committed to the DB...so as long as the push encounters 0 issues, > everything is fine. If however, you are using an escalation to process > some records, lets say 100 of them...and 3 of them will generate an error. > If using a Push action from a control form, as described, the escalation > will fire, kicking off the Filter, the Filter will perform the push, it'll > hit the first record that errors out, and the entire action is rolled back, > thus leaving 100 records needing to be modified by the escalation. If > however, the Escalation was making the changes to that record directly, 97 > of the records would be successfully processed, 3 of the records would drop > an error in the arerror.log file, and you would be left with only the 3 > error records. > > Sothe two are not unfortunately 100% the same...but similar to each > other, with limitations that may or may not make the use of the control > form viable or not. > > > On Thu, May 1, 2014 at 1:13 PM, Tanner, Doug > wrote: > >> ** >> >> We use a table/form (i.e. CMN:System Variables) that has one entry with >> multiple attributes, we have a large number of escalations doing many >> different things that look at the CMN:System Variables, and then runs >> appropriate actions on appropriate tables. Works slick! Doug >> >> >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> arslist@ARSLIST.ORG] *On Behalf Of *Ben Cantatore >> *Sent:* Thursday, May 01, 2014 12:18 PM >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: Self-Terminating/disabling Escalation >> >> >> >> ** Sapna, >> >> Have a flag field as part of the escalation set the flag to true. Make >> the run if qualification for the escalation run on flag equal false. That >> should ensure it only runs once. Otherwise, I'd just create an escalation, >> run it and then remove it manually. >> >> >> >> *Ben Cantatore* >> *Remedy Architect* >> Bed Bath & Beyond >> 650 Liberty Avenue >> Union NJ 07083-8130 >> Office: (908) 613-5769 >> Cell: (914) 263-6802 >> >> [image: LinkedIn] <http://www.linkedin.com/pub/ben-cantatore/3/220/9a7/> >> >> >> >> From:Sapna Motwani >> To:arslist@ARSLIST.ORG, >> Date:04/30/2014 11:58 PM >> Subject:Self-Terminating/disabling Escalation >> Sent by:"Action Request System discussion list(ARSList)" < >> arslist@ARSLIST.ORG> >> -- >> >> >> >> >> 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" >> >> "-- CONFIDENTIALITY >> NOTICE: This e-mail, and any attachments thereto, is intended only for use >> by th
Re: Self-Terminating/disabling Escalation
Short of creating an API program I bet driver.exe and a small script file can do it. https://docs.bmc.com/docs/display/public/ars81/Using+the+driver+program Jason On Thu, May 1, 2014 at 10:18 AM, Charlie Lotridge wrote: > ** > 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 > 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" >> > > _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"
Re: Self-Terminating/disabling Escalation
Cool, even better. Always good to know that something that I was told did not make it actually made it in. That makes the option I described an even cleaner match to the use case desired. Thank everyone for clarifying when I did not have the complete answer – and that is where the community comes together to help provide complete answers. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Westbrock Sent: Friday, May 02, 2014 11:03 AM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** I think that was in place as of version 7.6.04 since I remember right-clicking to run an escalation last year (but maybe my memory is faulty, I don’t have a 7.6.04 system to reference now). -Rick _ Rick Westbrock Remedy Administrator | IT Department 24 Hour Fitness USA, Inc. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Friday, May 02, 2014 9:18 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Self-Terminating/disabling Escalation ** Doug, I hate to contradict you, but, if you right click on any escalation, the bottom option is 'Run Now'so, at least in the 8.1 version of the Dev Studio, there is a GUI option that enables this. On Thu, May 1, 2014 at 1:22 PM, Mueller, Doug mailto:doug_muel...@bmc.com>> wrote: ** 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<mailto:arslist@ARSLIST.ORG>] On Behalf Of Charlie Lotridge Sent: Thursday, May 01, 2014 10:18 AM To: arslist@ARSLIST.ORG<mailto: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 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_ _AR
Re: Self-Terminating/disabling Escalation
Doug, I hate to contradict you, but, if you right click on any escalation, the bottom option is 'Run Now'so, at least in the 8.1 version of the Dev Studio, there is a GUI option that enables this. On Thu, May 1, 2014 at 1:22 PM, Mueller, Doug wrote: > ** > > 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 > 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" > > > > _ARSlist: "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"
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 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"
Re: Self-Terminating/disabling Escalation
Doug, “ A good enhancement request is to have the ability to say to "run now" for an escalation exposed through dev studio.” This is already available…. In Dev Studio v8.1, why can’t one just right-click and say “Run Now”? We’ve used this during a migration for a one time update. [cid:image001.png@01CF6578.69A73380] Thank you, Michelle From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug Sent: Thursday, May 01, 2014 2:22 PM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** 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<mailto: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 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_ _ARSlist: "Where the Answers Are" and have been for 20 years_ -- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Self-Terminating/disabling Escalation
We use a table/form (i.e. CMN:System Variables) that has one entry with multiple attributes, we have a large number of escalations doing many different things that look at the CMN:System Variables, and then runs appropriate actions on appropriate tables. Works slick! Doug From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Ben Cantatore Sent: Thursday, May 01, 2014 12:18 PM To: arslist@ARSLIST.ORG Subject: Re: Self-Terminating/disabling Escalation ** Sapna, Have a flag field as part of the escalation set the flag to true. Make the run if qualification for the escalation run on flag equal false. That should ensure it only runs once. Otherwise, I'd just create an escalation, run it and then remove it manually. [cid:image001.png@01CF654F.F2408490] Ben Cantatore Remedy Architect Bed Bath & Beyond 650 Liberty Avenue Union NJ 07083-8130 Office: (908) 613-5769 Cell: (914) 263-6802 [LinkedIn] From:Sapna Motwani mailto:sapana.motw...@gmail.com>> To:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>, Date:04/30/2014 11:58 PM Subject: Self-Terminating/disabling Escalation Sent by:"Action Request System discussion list(ARSList)" mailto:arslist@ARSLIST.ORG>> 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" "-- CONFIDENTIALITY NOTICE: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please permanently delete the original and any copy of any e-mail and any printout thereof. Thank you for your compliance." _ARSlist: "Where the Answers Are" and have been for 20 years_ This email is subject to certain disclaimers, which may be reviewed via the following link. http://compass-usa.com/Pages/Disclaimer.aspx. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Self-Terminating/disabling Escalation
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 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"
Re: Self-Terminating/disabling Escalation
Sapna You can create a form with the workflow (filters) actions you want to accomplish on you primary form This form will act as you trigger Set you Escalation to run on this trigger form. The Escalation can have a Run If Qualification of something like 'Status' = "Active" Then have part of the escalation action change the 'Status' to "In-Active" The Escalation continues to run on its set interval but finds no entries to match its Qualification Alternatively, you can have a couple escalations to change the trigger entry Status (1 to Activate, 1 to Deactivate) This allows you to setup a window of time where the trigger can be active on a reoccurring basis. Gregory Givens CTR NPC Remedy Admin -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sapna Motwani Sent: Wednesday, April 30, 2014 2:06 PM To: arslist@ARSLIST.ORG Subject: Self-Terminating/disabling Escalation 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"
Re: EXTERNAL: Re: Self-Terminating/disabling Escalation
Or Set it up to run every 99 days like Rick said and add AND $DATE$ = "05/01/2014" to your run if. It will run immediately today and by tomorrow the DATE check will be false. Since it only gets run every 99 days there is little impact on the system except to check the escalation and verify that it's counter has not expired and when it does expire the run If is still false. But I would still go back in and clean it up manually. Either disabling it or deleting it. Thank you, --- John J. Reiser Remedy Developer/Administrator Senior Software Development Analyst Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Westbrock Sent: Thursday, May 01, 2014 11:13 AM To: arslist@ARSLIST.ORG Subject: EXTERNAL: Re: Self-Terminating/disabling Escalation I don't know of a way to do that. When I need to have an escalation run only once I will either set it for an interval of 99 days (if I want it to run immediately) or for a specific day of the month and time. In either case you must go back and disable the escalation but that will give you 99 days or one month respectively to do so before it fires again. -Rick ___ 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"
Re: Self-Terminating/disabling Escalation
I don't know of a way to do that. When I need to have an escalation run only once I will either set it for an interval of 99 days (if I want it to run immediately) or for a specific day of the month and time. In either case you must go back and disable the escalation but that will give you 99 days or one month respectively to do so before it fires again. -Rick ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Self-Terminating/disabling Escalation
Sapna, Have a flag field as part of the escalation set the flag to true. Make the run if qualification for the escalation run on flag equal false. That should ensure it only runs once. Otherwise, I'd just create an escalation, run it and then remove it manually. Ben Cantatore Remedy Architect Bed Bath & Beyond 650 Liberty Avenue Union NJ 07083-8130 Office: (908) 613-5769 Cell: (914) 263-6802 From: Sapna Motwani To: arslist@ARSLIST.ORG, Date: 04/30/2014 11:58 PM Subject: Self-Terminating/disabling Escalation Sent by:"Action Request System discussion list(ARSList)" 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"
Self-Terminating/disabling Escalation
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"
