The cleanest implementation I've seen of this was where the data was segregated from the users through the use of DO forms. Basically, all 'user' interactions with the data were controlled through data pushes and pulls to the actual 'regular' forms. That being said, since the 'push' is a defined stage in the process flow, you are able to interrupt it at will. So, we had a common 'message' dialog that, based on the type (error, confirmation, warning, etc.) can return a value (Yes/No), stop processing altogether, or let it continue after the user confirms they read the message.
All the messages were stored in their own form, obviously, and could be coded as you wish (all errors have a specific range, etc.). Anyway, that's one successful, home-grown approach. Enjoy, Matt R. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Thursday, April 17, 2008 7:15 PM To: [email protected] Subject: Re: Open Window to act like an Error Message That is a good start... but.... It is possible that you might have nested workflow that would trigger other things even after execution order 1000 for the given "execute on" condition. So there may be other things that might also need to be done in some cases. Also... if the active link is in side a guide, then the goto action will not get the job done either. You may need to use the "Exit all guides" action to interrupt all running guides. (But again, that may still require other changes to really not trigger any other workflow.) Unfortunately, I think there is no other single "magic bullet" other than a real error. -- 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 Thu, Apr 17, 2008 at 6:49 PM, Rick Ponzo <[EMAIL PROTECTED]> wrote: > Lisa, > > After the call to the open window you can use a Goto Action and set the > execution order to 1000, which should be higher than any workflow that will > execute after it. > > Rick Ponzo > > > > > > Kemes, Lisa wrote: > > > ** > > > > I hate how the Messages look in the AR User Tool, so I create pretty > dialogue boxes and use the open window action to relay my messages. But when > it's an error message (and I want the action to stop) the Open Window Dialog > box doesn't work. (it works, but the action does not stop when they click > the close button, the action just keeps going) Whether it's a push, or set, > etc.action... > > > > Is there any way to make a "purty" error message? > > > > *Lisa Kemes/ /* > > AR System Developer > > Tyco Electronics > > 717-810-2408 tel > > 717-810-2124 fax > > [EMAIL PROTECTED] ____________________________________________________________________________ ___ 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"
