That would work, but I generally avoid GOTO in coding--both in Remedy development and in traditional coding.
GOTO leads to spaghetti code, in my opinion. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Monday, November 26, 2007 2:25 PM To: [email protected] Subject: Re: PERFORM-ACTION-APPLY Weirdness (UNCLASSIFIED) Norm, Well.. If you are sure you want to go that way... How about a GOTO statement in the first AL to "jump over" the second active link? -- 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 Nov 26, 2007 3:20 PM, Kaiser Norm E CIV USAF 96 CS/SCCE <[EMAIL PROTECTED]> wrote: > >I would avoid the wide open $OPERATION$ != QUERY because it will > probably get you into trouble. There are lots of different states > associated with the $OPERATION$ keyword. > > Thanks, but I want the workflow to fire in each of those states *other* > than QUERY, so my qualification is fine. Really that's not the issue. > > The issue, in my mind, is that workflow continues processing despite the > mode change...which I suppose isn't wrong, per se, just not what I > expect. > > Perhaps what I need to do is put a hidden display only field on the form > that gets set when the operation is begun and prevents the second AL > from firing. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
