I've had to do something similar before where I needed to get some info after an approval and refresh / redisplay the screen. You can set up an AL Guide to loop (make sure you have a counter set so that you have an exit strategy). Use an AL in the guide that does a set field back to form B of a value in the record in form C (can be set by the filters on form C). Basically the process looks like this:
Create an AL with the following actions Action: Set field of a counter to 50 - can be a different value based on how long the process takes Action: Call Guide Guide looks as follows: Label_Top Active Link Action: set field action from form C to set a field with a value from the record that indicates the RFC is done. Active Link with run if field = value (or field not $NULL$) Action : Exit guide Else Action : counter = counter - 1 Active Link with run if counter > 0 Action goto guide label "Label_Top" End of guide. then your AL to read the results (or the results within the guide can be the return value(s) you need. The counter will help you fall out of the guide should the RFC go south. Hope this helps get you started. ----- Original Message ----- From: "prakash kodali" <[email protected]> To: [email protected] Sent: Thursday, February 7, 2013 5:34:21 PM Subject: Re: Open Window - Dialog - Commit Changes. ** Thanks for the replies. But here is my actual scenario. I have display-only form A (Parent window) and opening a regular form B in a new window of Dialog type(Child window). Child window B has some fields and a button. On click of button I need to execute a Web service and parse the results back to the child window fields. For this I have created another regular form C and created filters on form C to call the Webservice and stored returning result in a field. Now when I do 1. AL Push the values from Form B to Form C which in turn filters will execute RFC. 2. After push, reading the results from Form C. But the AL pushes and tries to read the results from Form C before filters executes RFC on Form C. My ALs on Form B should wait after push and until the Form C executes filters . Then It should read the results from from Form C. Hope it is clear and help me with any ideas to over come this problem. Prakash. On Thu, Feb 7, 2013 at 7:19 AM, Longwing, LJ CTR MDA/IC < [email protected] > wrote: Prakash, A Dialog window cannot, and shouldn't fire Filters on Commit. A Dialog window is NOT a record, it as a console. If you want to fire Filters that fire on Modify, you need to be modifying a record (which a Dialog window isn't doing)....so you could in theory do an AL Push to the record in question which would cause the filters to fire on Modify...that would be the simplest way to get where you want to go from where you are I think. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] ] On Behalf Of Prakash Kodali Sent: Wednesday, February 06, 2013 5:14 PM To: [email protected] Subject: Open Window - Dialog - Commit Changes. ** Helloo Listers, I have end up with a strange behavior of Open Window of DIALOG type and commit changes has no effect. I have even tried "PERFORM-ACTION-ACTIVE-LINK 4" / "PERFORM-ACTION-ACTIVE-LINK 8" to submit the form to trigger the filters. But of NO use. Any ideas/suggestions are highly appreciated on how to submit a Dialog window and trigger the filters? Please let me know, If I am not clear. Thanks Prakash. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
