Offhand question … Did your Push fields try to do a search or just create new?
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Wednesday, July 23, 2014 5:01 PM To: [email protected] Subject: How to execute AI jobs from workflow ** I know that Event driven AI jobs are possible, because the documentation says so. And in spite of that, the system architecture does seem to allow them. However, I am finding it elusive to actually do. I have a Transformation that I can run successfully manually. I put that into a Job that I can also run manually, and can schedule to run. I can also execute the job by creating a record manually in the UDM:Execution form. The final step would be to have some other AR System action create that record. It would stand to reason that any action against any form that could execute a piece of workflow could create the record there. So I created a custom DO form, copied the fields from the UDM:Execution on it, and added a button imaginatively entitled "Push to Run" which runs a Push Fields to the UDM:Execution form. Push the button, and I get an error message: "ARERR [8753] Error in plugin : Get List Entry With Fields not supported on form UDM:Execution". Thing is, no GLEWF even shows up in the API log for the transaction. So, I'm kinda stuck for what to try next. I suppose I could create a batch file with the command line argument in it, but that's not as user-friendly as the form solution. And I suspect I would get the same error anyway. Any ideas? Rick _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
