>I agree with not using != QUERY. Using that has bitten me in the butt a few times when a year later you open the same form in Dialog mode and unexpected workflow is firing.
Yes, folks, 9 out of 10 times I agree about the != QUERY. But in this case I want the workflow to fire in *EVERY* mode that is not QUERY. That includes DIALOG...not that the form in question would ever be opened as a dialog, but if it ever were, I'd want the workflow to fire. ------------- Dylan Wheeler Production Control Analyst Principal IT Operations Downey Savings & Loan Association, F.A. Email: [EMAIL PROTECTED] -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Monday, November 26, 2007 12:28 PM To: [email protected] Subject: Re: PERFORM-ACTION-APPLY Weirdness (UNCLASSIFIED) 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" This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. ________________________________________________________________________ _______ 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"
