I just looked at the code I use... I am doing both the external script (Action 1 of my Filter) and the PERFORM-ACTION-ADD-ATTACHMENT (Action 2 of the same Filter) as Set Fields $PROCESS$ actions.
The main thing is that what you are doing is working for your users. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ashcraft, Roy W. Sent: Thursday, August 17, 2006 11:50 AM To: [email protected] Subject: Re: RESOLVED - Putting a Character Field into an Attachment Field I tried that. The file was still not available in the filter stack. Roy -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Thursday, August 17, 2006 11:26 AM To: [email protected] Subject: Re: RESOLVED - Putting a Character Field into an Attachment Field Run your external script from a Set Fields $PROCESS$ action instead of a Run Process action. It then runs in phase 1. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ashcraft, Roy W. Sent: Thursday, August 17, 2006 11:09 AM To: [email protected] Subject: Re: RESOLVED - Putting a Character Field into an Attachment Field Just wanted to thank everyone for their suggestions. Eventually, I ended up writing an external script and added a couple of flags to the underlying form. The attachment field isn't updated immediately, which is what I wanted, but it is updated in a few minutes, which is good enough for the customer. When the long character fields are updated, status is changed to pending. An escalation runs on all records with a "Pending" status, running the script and creating the files with identifiable filenames, then sets the status to processed. A second escalation runs on all records with a status of "Processed" and does a PERFORM-ACTION-ADD-ATTACHMENT to pull the files into the attachment fields. Tried doing the above from filters - one immediate (`!) filter to push the values to another form for an immediate submit, next filter with a set fields $PROCESS$ to run the script and another filter to bring the files into the attachment fields. Several problems with this. The AR System didn't do the COMMIT action on the database for the immediately push (except on submit) until after the filter stack completed - kind of screwed up what data ended in the files. Another was that even with the set fields $PROCESS$, the files weren't available for the ADD-ATTACHMENT action. Which is why this is broken out into two separate escalations so that everything is complete before the next action occurs. Thanks again for the help, this was the last challenge to complete our data-driven notification feature for the help desk. Thanks, Roy Roy Ashcraft Systems Analyst SAIC [EMAIL PROTECTED] (402) 293-5218 ________________________________________________________________________ ____ ___ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
