Thanks everyone for your assistance. Eric Alfonso, Contractor, 95 CG/SCCSS DSN 525-9192 COMM 661-275-9192 Remedy Support Team [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Tuesday, May 01, 2007 7:15 AM To: [email protected] Subject: Re: Forcing escalations to run in sequence and not starting until previous is completed ** There are a number of things you can look for...you could check that the Last Modified By is equal to AREscalator and that the Modified Date is close to the time you expect the modification to have occurred. That way the filter won't fire when the record is modified by Joe Blow user. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Alfonso Eric B Contr 95 CG/SCCSS Sent: Monday, April 30, 2007 6:10 PM To: [email protected] Subject: Re: Forcing escalations to run in sequence and not starting until previous is completed Thanks. I thought about that. I need to determine what to use as the value to trigger each filter. Eric Alfonso, Contractor, 95 CG/SCCSS DSN 525-9192 COMM 661-275-9192 Remedy Support Team [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Monday, April 30, 2007 12:59 PM To: [email protected] Subject: Re: Forcing escalations to run in sequence and not starting until previous is completed ** Replace the "subordinate" escalations with filters. For example, I assume you have something like this now: Escalation 1 fires at 12:00 Escalation 2 fires at 12:15 but is dependent on 1's success What I suggest is replace Escalation 2 with a filter. Set that filter to run on modify and have it look for the expected value set by Escalation 1. HTH, Norm ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Alfonso Eric B Contr 95 CG/SCCSS Sent: Monday, April 30, 2007 12:41 PM To: [email protected] Subject: Forcing escalations to run in sequence and not starting until previous is completed Hi everyone, I am new to Remedy development and recently completed a full active directory integration with Remedy v.7. It takes several escalations running in sequence each night to keep the various location and people related forms updated. I have the escalations running at pre-determined times in sequence. Is there any way to set one escalation to trigger the start of the next which will trigger the start of the next, etc, without using the time as the trigger? There are times when the previous escalation fails and I would like it to prevent the next one from firing when this occurs. Thank you, Eric Alfonso, Contractor, 95 CG/SCCSS DSN 525-9192 COMM 661-275-9192 Remedy Support Team [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
