Aah yeah, I found this in the documentation, so it looks like the way to trigger an AI job is basically to push the right values into "Application Pending" (at least on 8.1.01):
https://docs.bmc.com/docs/display/public/ac81/Setting+up+event-driven+jobs+in+Atrium+Integrator I think from there, I can probably watch the various log forms (UDM:TransformationLog, UDM:StepLog etc) to try and catch errors, status, etc. Though identifying MY specific job versus any other random job that might be running at the time ... I'm not quite clear on that (yet), but .... really what I'm struggling with now, is how to send a variable into the AI job. Just one would do. If I could send a GUID or something into the job, that'd be good enough to glue everything together (for instance I can use the GUID to reach back into the DB and find my attachment filename, identify my logs from all the others, etc). Thing is ... so far ... I just don't see a way to do something like that, but maybe I'm just barking up the wrong tree and there's a "right" way to do this? I see a few suspiciously "extra" fields on Application Pending ('Field 1', 'Field 2', 'Other Short', 'Other Long', etc). That is certainly the sort of thing I'd put on a form to send arguments to a job, but as to how specifically these are used (if at all) ... God, it's just anyone's guess because there's absolutely zippy mention in the documentation (that I can find at least). Any more help out there? LOL :-) thanks everyone! -Andy On Mon, Aug 3, 2015 at 11:28 AM, Rick Cook <[email protected]> wrote: > ** > > I've done it, though my memory is fuzzy on the details. Basically, when > you schedule your AI job, it creates a record in a form. The form name > depends on the version of AI, but it's in the docs. > > You can have workflow look for records matching your criteria entering > that form, and do what you want with it. > > Rick > On Aug 3, 2015 8:04 AM, "Andrew Hicox" <[email protected]> wrote: > >> ** >> >> Hi everyone, >> >> I have a requirement to create a user interface whereby a spreadsheet is >> uploaded as an attachment, and used as an input to an atrium integrator job >> that will import/mangle data appropriately. >> >> Offhand, it seems like this ought to be possible. I suspect I could use >> a clever run-process to copy the attachment into a temp directory and have >> AI pick it up from there. >> >> However, I need some way of not only triggering the AI job in real time >> from workflow, but I also need a way to send a variable into the job at >> runtime (i.e. "process this specific filename right now"). Also (ideally) >> I'd need some way of capturing exceptions from AI and displaying a sensible >> error message to the user ("missing required data", "bad spreadsheet >> format", etc etc). >> >> Has anyone here ever attempted this sorta thing? If so, any pointers? >> >> -Andy >> _ARSlist: "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"
