I think the escalation solution is the best. If Parent Request ID = $NULL$ and Child Detail is older than 24 hours, delete Child Detail. Thank you very much, Christie and Robert. ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Robert Molenda Sent: Friday, August 17, 2007 10:44 AM To: [email protected] Subject: Re: Window Close condition ** Michael; Using "Close Window" action is not going to achieve what you are desiring to do, and there are few other oddities about "On Window Close" activity... IF you switch from Search to New = Window Close Action IF you switch from New to Search = Window Close Action IF you perform a search and when the record list is displayed = Window Close Action AND as you have noticed: Edit record -> Big X button -> Window Close Action -> Dialog box asking to SAVE (although window is still alive) Do not ask ME why, because in normal "window programming", it should only happen when the logical form is destroyed... What I would suggest unfortunately, is at the time the "Parent Form" is saved, a filter will do a modify-all on the child-form records to set a flag that the parent was created. Then you can run a periodic escalation to remove child-form records in where the parent form was never created... HTH Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Durrant, Michael M. - ITSD Sent: Friday, August 17, 2007 8:31 AM To: [email protected] Subject: Re: Window Close condition hmmm... I think I need to explain myself in a little more detail. I have a parent form which I can add child records to. I've created a GUID/timestamp field that I use to relate the child form to the parent form until the parent form has been saved and I have a request ID to relate by. If the user closes the parent form without saving it, I want to delete the child records that were created. Currently, I have the active link set to fire on Window Close with a qualification of "'Request ID' = $NULL$" (indicating that the parent request hasn't been saved yet) - it executes a run process Application-Query-Delete-Entry to delete all the child records that match the GUID/timestamp field. That works as expected, with the exception that it runs before the user actually CLOSES the form. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pargeter, Christie Sent: Friday, August 17, 2007 8:57 AM To: [email protected] Subject: Re: Window Close condition ** I have made 2 buttons on my screen to do this sort of thing. 1 - Save & Close 2 - Don't Save & Close The Save & Close has 2 ALs the first does the PERFORM-ACTION-APPLY and the 2nd AL does the close window. Since it is not in the same AL and they do not pass a filter it will stop the close window action. The Don't Save & Close sets the change flag on the form then closes the window. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Durrant, Michael M. - ITSD Sent: Friday, August 17, 2007 7:52 AM To: [email protected] Subject: Window Close condition ** ARS 7.0.01 I have an active link that fires on Window Close. The problem I have is: 1) User modifies form 2) User closes form without saving and is prompted to save due to changes. You would think the AL would fire only if the user confirmed closing the window. Au contrare - it fires as soon as it prompts the user. If the user presses Cancel, the action has already fired. Am I using this thing right? Is there another condition I should be looking at? Thanks for your time - Michael The information contained in this email may be privileged, confidential or otherwise protected from disclosure. All persons are advised that they may face penalties under state and federal law for sharing this information with unauthorized individuals. If you received this email in error, please reply to the sender that you have received this information in error. Also, please delete this email after replying to the sender. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ The information contained in this email may be privileged, confidential or otherwise protected from disclosure. All persons are advised that they may face penalties under state and federal law for sharing this information with unauthorized individuals. If you received this email in error, please reply to the sender that you have received this information in error. Also, please delete this email after replying to the sender. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ The information contained in this email may be privileged, confidential or otherwise protected from disclosure. All persons are advised that they may face penalties under state and federal law for sharing this information with unauthorized individuals. If you received this email in error, please reply to the sender that you have received this information in error. Also, please delete this email after replying to the sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
