You could create a field that the escalation sets and then if you want you
could also use that in combination with last modified by of AR_ESCALATOR.
The filter is going to run as soon as the record is modified by the
escalation.  You could also have the filter null that field also so it's
always null until the escalation sets it.

Susan


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] <[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:* arslist@ARSLIST.ORG
*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:* arslist@ARSLIST.ORG
*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]
__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"

Reply via email to