Mathieu, Page 634 of BasicGuide.pdf for a few examples. Section "Example of sending events between windows".
-- 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 11/15/06, Mathieu Pitre <[EMAIL PROTECTED]> wrote:
Thank you Carey, I understand your suggestion and actually I tough about it but I could not figure what would be the PERFORM-ACTION-SEND-EVENT parameters. What am I going to use? PERFORM-ACTION-SEND-EVENT $189787464$ "GetCatalogueEntry" (189787464 would be the field ID containing the CURRENTWINID value)? Thank you in advance. Mathieu Pitre IT Business Systems Analyst Production Operation Computer Sciences Corporation Pratt & Whitney Canada, Plant 1 Sametime: Mathieu Pitre office: 450-647-8008 x7030 Carey Matthew Black <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 15/11/2006 09:16 AM Please respond to [email protected] To [email protected] cc Subject Re: Send Event to Specific window Mathieu, The PERFORM-ACTION-SEND-EVENT function can send to a specific Window ID, but you need to know what Window ID to send it to. Can you do something like the following in your workflow? When the user opens the "Software Catalog" window pass in (to a display only field) the value for $CURRENTWINID$ from the "Release-Request" form. Then when the "Clone" button is pressed, have the "Clone" window hang on to that value ($CURRENTWINID$) from the "Release-Request" form. Then finally when the "Clone" window is closed send the event to that WINID value. I think that will work, but because there is "other stuff" that your workflow is doing it might be easier or harder to implement depending on the details. For example you might need another display only field to identify a "clone" "Software Catalog" window vs a "Software Catalog" window to manage when the event should or should not be sent on Window Close. HTH. -- 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 11/9/06, Mathieu Pitre <[EMAIL PROTECTED]> wrote: > Hi all, > > ARS6.3 > HP-UX 11.11 > > I am having a hard time to use Receive an Event in one of my application. > > Here are the elements involved: > > Release-Request = Form1 > Software Catalogue = Menu > Create Catalogue Entry = Button > > Catalogue = Form2 > Clone = Button > Save = Button > Exit = Button > > Here is the scenario: > > I select an application from my Software Catalogue Menu and I click on the > Create Catalogue Entry button to access the selected software in the > Catalogue form. Once the Catalogue form opens, the user clicks on the > button clone to create a clone of the catalogue entry. The user changes the > software version and save the form using the save button. Finaly, he/she > clicks on the exit button to close the form. At that point, I fire an > Active Link to send an Event to my Release-Request form which is still > opened. The Release-Request form should receive the event to update the > value in the Software Catalogue menu to correspond to the lastest created > software(Clone). However, my Release-Request never receives the event > because it does not seem to be the parent form anymore. I think that it is > due to the actions used within the clone Active Link. The clone AL closes > the current window and do other stuff. In the log file, I can see that the > Event is sent by never received on the other side. > > Is there anything I can do to Send the Event to a specific window? I am > current use the following Process to push the Event: > PERFORM-ACTION-SEND-EVENT @ "GetCatalogueEntry" > > I cannot used the "*" in the PERFORM-ACTION-SEND-EVENT because several > Release-Request might be opened at the same time and therefore all of them > are going to execute the Event. > > Let me know I you need more info. > > Regards, > > Mathieu Pitre > Business Analyst > CSC
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
