I agree with David, Scott, and Thad. You cannot perform actions on a separate window than the window from which you opened the active link without creating a new active link. Also, your Close action is killing the active link. Additionally, in the log, you are definitely seeing the continuation of the active link that opened the dialogue window, hence the next action is 1) instead of 2). The active link you mention originally has four steps:
0) Push Fields - to a supporting table 1) Close Window 2) Set Fields - I am setting a field using COLSUM 3) Change Field - simply refresh a table field You see steps 0 and 1 fire, 1 being the close window. Then you see later it picks back up with a step of index 1. If this Wait was indeed part of your original AL you mentioned, it's index would have to be 2, since 0 and 1 were already fired, which leads me to concur with Scott, David, and Thad that the Wait and the Refresh we are seeing are coming from the original AL that fired an Open Window on action 0, then the Wait on action 1, and the Refresh on action 2. Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thad K Esser Sent: Tuesday, September 11, 2007 11:23 AM To: [email protected] Subject: Re: Workflow will not fire? ** Brian, >From your logs... the SCHN-PO4PushNonStandardItem AL is the one you are concerned about, but notice... you said it has 4 actions: 1) Push Fields - to a supporting table 2) Close Window 3) Set Fields - I am setting a field using COLSUM 4) Change Field - simply refresh a table field In the logs, your push fields is the one that starts with "0:", the Close window starts with "1:", then you see the Close Window actions logged. Now look at the line right after the "Stop active link processing - On Window Close" line. It says: <ACTL> 1: Wait <ACTL> Continue: Continue <ACTL> 2: Set Characteristics <ACTL> For field -- Table Field (536871020) <ACTL> Refresh field That line "1:Wait" is coming from the active link that opened the dialog, not from SCHN-PO4PushNonStandardItem. Likewise with the "2:" table refresh (it's the 3rd action on the calling AL). So neither the 3rd nor 4th action of SCHN-PO4PushNonStandardItem is being run (i.e. everything after the close window). I think the confusion is because the table was being refreshed, but that is from different workflow than you thought. Hope that helps, Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "Sokol, Brian" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/11/2007 08:21 AM Please respond to [email protected] To [email protected] cc Subject Re: Workflow will not fire? ** David it is a dialog but simply another view of the same form so it should work. I see in the AL log that once the dialog window closes the calling AL continues. Here is a piece of the log. You can see the continue statement. Action 4 (Refresh field) fires but not action 3. <ACTL> Checking SCHN-PO4PushNonStandardItem (0) <ACTL> -> Passed qualification -- perform if actions <ACTL> 0: Push Fields <ACTL> To Schema SCHN-POLineItem on Server @ <ACTL> (536870914) = 1 <ACTL> (536871019) = PO001279D84E93lZ_mRgSDAhQwivxE <ACTL> (536870917) = 1 <ACTL> (536880934) = <ACTL> (536880935) = <ACTL> (536870913) = 1 <ACTL> (536870916) = 11.330 <ACTL> (536870915) = 11.33 <ACTL> 1: Close Window <ACTL> /* Tue Sep 11 2007 10:01:47 */ <ACTL> --1-- Start active link processing -- Operation - On Window Close <ACTL> For Schema - SCHN-PO4 <ACTL> On screen type - DIALOG <ACTL> /* Tue Sep 11 2007 10:01:47 */ <ACTL> --1-- Stop active link processing - On Window Close <ACTL> 1: Wait <ACTL> Continue: Continue <ACTL> 2: Set Characteristics <ACTL> For field -- Table Field (536871020) <ACTL> Refresh field <ACTL> /* Tue Sep 11 2007 10:01:47 */ ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of David Sanders Sent: Tuesday, September 11, 2007 11:12 AM To: [email protected] Subject: Re: Workflow will not fire? ** Hi Brian Am I right in thinking that the active link is running on a button click in the dialog, but action 3 is trying to perform a COLSUM against the table on the parent form? - if so, this will not work. You need to split this into separate active links on each of the 2 forms as follows: Parent form - active link on button click opens dialog form Dialog form - active link on button click pushes data to backend form, (commits changes and) closes dialog window Parent form - active link (checks for result of commit from dialog, and) refreshes table and does COLSUM set fields. Note that the 2 active links on the parent form could be a single active link if you do not care to check the result passed back from the dialog in the Close Window mapping. Opening the dialog form in dialog mode will stop processing the active link on the parent form until the dialog has been closed. If your COLSUM needs to take account of the new record created by the push fields, you should do the refresh before you do the COLSUM operation. HTH David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application See the ESS Concepts Guide <http://www.westoverconsulting.co.uk/downloads/ESS_Concepts_Guide.pdf> tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/> ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sokol, Brian Sent: Tuesday, September 11, 2007 3:54 PM To: [email protected] Subject: Re: Workflow will not fire? Hi Roger, I have a display only form with a table of items. This is a purchase request form. A user can select one of the items and a quantity and click on the Add To PO button. This performs the same actions as the AL I am having problems with except there is no Close Window action. This all works OK and the COLSUM function works. If a user needs to order a non-standard item (one that is not listed on the form) they click on a button and open a Dialog box. This dialog box is a different view of the same display only form. They fill in a few fields including quantity and price. They then have to click on the same Add To PO button to perform the 4 actions I listed below. Actions 1, 2 and 4 always fire. Action 3 never fires and is never listed in the AL log. Hope this clears this up. thanks, Brian ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger Sent: Tuesday, September 11, 2007 10:38 AM To: [email protected] Subject: Re: Workflow will not fire? ** The first thing that comes to mind is how many forms are you working with? Because of the Close Window action it sounds like there are two. Thanks, Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sokol, Brian Sent: Tuesday, September 11, 2007 10:26 AM To: [email protected] Subject: Workflow will not fire? I have an active link that has 4 actions in it. When a button is pushed the following actions should occur: 1) Push Fields - to a supporting table 2) Close Window 3) Set Fields - I am setting a field using COLSUM 4) Change Field - simply refresh a table field Actions 1,2 and 4 always fire. I can never get action 3 to fire. If I look at the Active Link log it never shows as if it does not exist. I know I experienced this same type of problem some time ago where some workflow was just ignored. I am on ARS 7.01 patch 1 on SQL 2000/Server 2003. Anyone have an idea to try? thanks Brian Sokol Manager, Desktop Services Scholastic Inc. 557 Broadway NY, NY 10012 (212) 343-6494 http://www.Scholastic.com <http://www.scholastic.com/> __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
