What I have done in the past to do a complete guide exit within nested
guides is when your conditions are satisfied (or not, depending on your
code), I do a GOTO label action, such as "EXIT", there is only one active
link after that label and that does the Exit all guides action.
Start
AL1
AL2
AL3
Exit
AL (Exit all guides)
Edward Hum
ITIL V3 Foundation Certified
BMC Software Certified Consultant ITSM 7.x - IM/PM/AMD
Phone: +01-905-231-1631 Email: hum.edw...@gmail.com
http://www.linkedin.com/in/edwardhum
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
Sent: Monday, June 15, 2009 5:41 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
Despite never having used nested al guides AND an 'exit all guides'
action, your and my understanding are essentially the same. I would see
if I was able to replicate the functionality in a small form with sample
workflow with 'you should never get this message' messages in the first
level, and see if you can stop the processing. If you can't, definitely
log a bug, if you can, then further analysis is needed to determine what
is different between your scenario and the simplified version.
________________________________
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Monday, June 15, 2009 3:36 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
Sorry, I wasnt clear. The workflow that Im trying to get to work
doesnt actually fire an error. Im checking for my defined error
conditions (e.g., required fields not being filled in) and then
displaying an error message in a custom dialog. At that point, I call
the Exit Guide with Exit All Guides selected to stop processing at that
point. That doesnt seem to be working, though, and Im not sure why.
The guide its been called from at this point is nested down a couple
levels, and it manages to stop processing in the guide immediately above
it, but not the one above that. So, my Save Records guide stops
executing and doesnt save the record, but the Submit Record guide still
completes (which tells the user that the record was saved successfully)
even though there is an error condition that called Exit All Guides.
Does that make sense?
As I understand it, the Exit All Guides option should have cause all
three guides to stop processing at that point. Am I misunderstanding
something?
Thanks,
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
Sent: Monday, June 15, 2009 3:28 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
Errors stop processing immediately, so an exit guide after an error
message would never fire. You could try moving it to prior to the
error, then throw the error?
________________________________
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Monday, June 15, 2009 3:06 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
Then that sounds like it probably wont do what I want, because I want
processing to stop at that point. That was the point of adding the Exit
Guide after I display the error message. That just doesnt seem to be
working the way I thought it would
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of LJ Longwing
Sent: Monday, June 15, 2009 3:00 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
Error handlers fire on ANY error condition, be it system or human. If
you however generate an error handler for a user error, and don't
display the error, your handler filter needs to do whatever to correct
the problem because if you don't throw an error at the end of it then
the transaction gets committed to the DB.
________________________________
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Guillaume Rheault
Sent: Monday, June 15, 2009 2:53 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
good question. I have not tested the error handling filters with a user
generated error message, only with system error messages, but it should
work.... give it shot. The error handling feature kicks in when the
filter encounters an error. The documentation is not clear about whether
it is a system error or a "user" error, so the only way to find out is
testing it...
Guillaume
-----Original Message-----
From: Action Request System discussion list(ARSList) on behalf of Lyle
Taylor
Sent: Mon 06/15/09 4:49 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
Would that work even with user-generated error messages, since I'm not
trying to trap a system error? In this case, I've defined an error
condition and am checking for it and then trying to raise that error to
the user in a friendly way while stopping further processing. I know I
can display a Message of type Error, but that is what I'm trying to
avoid. If I "display" a Message of type Error and then define an error
handler, will it keep that message from popping up?
Thanks,
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Guillaume Rheault
Sent: Monday, June 15, 2009 2:39 PM
To: arslist@ARSLIST.ORG
Subject: Re: Exit Guide Problem
**
With the 7.1 error handling feature you could trap the OOB error message
and display your own user friendly error message. You'd use the $ERRNO$,
ERRMSG$ and/or the $ERRAPPENDMSG$ keywords in the qualification of the
error handling filter
Guillaume
-----Original Message-----
From: Action Request System discussion list(ARSList) on behalf of Lyle
Taylor
Sent: Mon 06/15/09 3:31 PM
To: arslist@ARSLIST.ORG
Subject: Exit Guide Problem
Hi all,
ARS 7.1
I'm having what I think is an issue with some Active Link Guides and an
Exit Guide action that isn't working the way I was expecting. The short
of it is that I was trying to provide a more user friendly experience by
displaying a custom dialog for errors encountered during data validation
rather than popping up an OOB Error Message. The workflow is written so
that if an error doesn't occur (i.e., workflow processing actually makes
it to that point), then it assumes that everything's OK and does the
rest of the actions. The problem I'm having is that I'm calling a
couple guides from within another. In one of the nested guides, I have
an Exist Guide action with "Exit All Guides" checked. My understanding
of this was that at this point, all the guides in the "stack" would stop
processing at that point. This doesn't appear to be happening, however.
The two inner guides appear to stop at that point, but not the outer
one.
What I've got is something like this:
ALG - Submit Record
AL - Save Record
AL - Disable Submit Button
AL - Display Successful Submission Message
The Save Record AL simply calls another Active Link Guide:
ALG - Save Record
AL - Check Required Fields
AL - Push record to base form
The Check Required Fields AL calls yet another Guide:
ALG - Check Required Fields
AL - Check Field 1
AL - Check Field 2
AL - Exit Guide (if none of the Check field actions
encountered any issues, then this guide only will get exited)
Label: Required Field Missing
AL - Display Message Dialog with Error Info
All the Check Field active links simply set the error message and then
go to the label. The "Display Message Dialog with Error Info" opens
the dialog with the error message and then has an Exit Guide action with
Exit All Guides selected. This should cause it to exit the Save Record
guide before saving the record as well as the Submit Record guide before
disabling the button and displaying the success message. The problem
is, it is only working part of the way. The record doesn't get saved,
so it does appear to be exiting the Save Record guide properly.
However, it still runs the rest of the Submit Record guide.
Any ideas why it might be behaving this way?
Thanks,
Lyle Taylor
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers
Are"_
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.71/2178 - Release Date: 06/15/09
17:54:00
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
