Satya (Consultant), You said: "the else actions are not fired."
But you did not say what the actions were doing. The important thing to know about Else actions for Escalations is that they "fire" in a special "null" context and only once. They have no record to operate on so they only have access to Display only fields on the form that they fire on. I also think that they do not even fire "Modify" filters on the form since they are not updating any record. Maybe the logic that you put in the Else action was assuming that filters would be fired? -- 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 9/18/07, Satya Gandhi <[EMAIL PROTECTED]> wrote: > ** > Dear Listers, > > I have an escalation that fires every hour and checks for a particular > condition on Form A. > > > The If Actions definted in the escalations are fired appropriately. > > I have a couple of actions definied in the Else Actions tab and if the > Escalation Run If Condition fails the else ations are not fired. > > Is this a known behaviour of escalations? > > I can always right a second escalation whose run if condition will be > different from the one on the original escalation and define the actions on > the IF Actions tab itself. But I dont want to increase the number of > escalations as there are numeours other escalations running on this server. > Is there anyother way I can achieve this? > > -- > Thanks & Regards > > Satya Gandhi > > Consultant - Remedy _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
