Alfonso, I think the real point here is to define when a "previous escalation fails" and what to do when that happens.
You have a linked set of processes that must be completed in sequence. But the trick is to have a test that identifies the success of each process and record it somewhere so that the next process can decide to run or not. I would suggest that you establish a "controller form" that could be as simple as a single record with a selection field with values for each process. When the first process finishes it should set the selection field to the process to "run next". In the event of a a "failure" you can opt to leave the selection field value alone but set the 'Status' to "Error" (or some such value) and do a notification to let someone know that manual intervention is needed. HTH. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 4/30/07, Alfonso Eric B Contr 95 CG/SCCSS <[EMAIL PROTECTED]> wrote:
** 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] ________________________________ 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]
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
