Attaching Files to a workflow instantiated from the command line

JMcNeil

Hey all,

Basically we would like to have an OpenDeploy DNR kick off a workflow with the files it has just transferred to the TS server.

Unfortunately iwjobc (or since we're using models iwmodelc) doesn't accept any sort of file attachment parameters.

What do you guys think is the best way to do this? I considered writing a perl script to call the iwmodelc, then take the returned id, get the current task, and attach the files to that task, then transition that task using iwcallback. Only problem with that approach is what kind of task to use that will just sit there waiting to be transitioned (I imagine external task, but it needs a command to run).

So not too sure what the best method here is, any suggestions?

Adam Stoller

Hey all, Basically we would like to have an OpenDeploy DNR kick off a workflow with the files it has just transferred to the TS server. Unfortunately iwjobc (or since we're using models iwmodelc) doesn't accept any sort of file attachment parameters. What do you guys think is the best way to do this? I considered writing a perl script to call the iwmodelc, then take the returned id, get the current task, and attach the files to that task, then transition that task using iwcallback. Only problem with that approach is what kind of task to use that will just sit there waiting to be transitioned (I imagine external task, but it needs a command to run). So not too sure what the best method here is, any suggestions?

Is there a WFM counterpart to iwwft_compile.ipl?

If you have a WFT - you can use iwwft_compile.ipl which takes a series of parameters (run iwperldoc iw-home/bin/iwwft_compile.ipl for more details)

If that CLT doesn't work for WFM's - and they didn't supply a corresponding CLT for it - contact Support and ask for it to be done.

(hopefully you folks will get all the kinks worked out before I have to do any significant work on 6.7x ;-)