My thought was that you would include error checking as well on close. So in this case you could add an error on close that if the selection field is blank fire an error so that the dialog cannot close unless a selection is made.
Todd Arner -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kaiser, Norm E CIV USAF AFMC 96 CS/SCOKT Sent: Thursday, July 30, 2009 2:07 PM To: arslist@ARSLIST.ORG Subject: Re: Disable Red "X" The problem is when the dialog is designed to force a selection from a multi-value field. For example, suppose the dialog pops and asks the user to select a value from a dropdown. Users have become conditioned to "If I see a red X, I click it to get rid of the popup, no matter what." When this happens, the dropdown doesn't get selected and a NULL value gets returned to the parent form. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Arner, Todd Sent: Thursday, July 30, 2009 7:09 AM To: arslist@ARSLIST.ORG Subject: Re: Disable Red "X" ** You might want to consider having your workflow fire on windows close rather than on a button click. For instance clicking on the save button could simply close the window and then on windows close fire the rest of your workflow. That way if they click the button it fires or if they just close the window it will fire. Todd Arner Great Lakes ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Brittain, Mark Sent: Wednesday, July 29, 2009 11:09 AM To: arslist@ARSLIST.ORG Subject: Disable Red "X" ** --> Hi All, Is there a way to disable the close window X in the upper right corner of a dialog? Depending one of several sets of criteria, when a ticket is closed, a dialog window opens asking a series of Yes/No questions before they can save the ticket. Problem is the users are using the X in the upper right hand corner to close the dialog window which breaks the workflow. Because of the many criteria's used I really don't want to have to add a field like "Questions Answered" since it might conflict with those users who don't need to answer the questions. ARS 6.3 patch 20 Thanks Mark ____________________________________________ Mark Brittain Remedy Developer NaviSite mbritt...@navisite.com <mailto:mbritt...@navisite.com> (315) 453-2912 x5418 (Phone) (315) 317.2897 (Cell) Reduce Cost of IT with Managed Hosting and Application Services from NaviSite. Visit www.NaviSite.com Today. ________________________________ This e-mail is the property of NaviSite, Inc. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited. _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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
