Getting job or task id

I know that the job id and the task id are passed implicitly to scripts called from an externaltask, but is there an easy way to derive those values from a TPL script called from the script called from an externaltask? For some reason, iwgetfilejobs is not returning any values, even when run from the command line.

My first thought, after discovering that iwgetfilejobs would be no help, was to simply pass the values as arguments to the called script, but this externaltask script is used by several different workflows to call TPL files, so they would all need to be retrofitted.

My current clunky solution is to run iwgetwfobj and extract either the activeworkflows or activetasks sections. I then iterate backwards through the list, figuring that the active job or task is among the last ones in the list, until I find one whose list of files contains the current DCR path.

There's got to be a more elegant solution, doesn't there?

Thanks, Dan

Find more posts tagged with

Comments

ISCBorisB

I know that the job id and the task id are passed implicitly to scripts called from an externaltask, but is there an easy way to derive those values from a TPL script called from the script called from an externaltask? For some reason, iwgetfilejobs is not returning any values, even when run from the command line.

My first thought, after discovering that iwgetfilejobs would be no help, was to simply pass the values as arguments to the called script, but this externaltask script is used by several different workflows to call TPL files, so they would all need to be retrofitted.

My current clunky solution is to run iwgetwfobj and extract either the activeworkflows or activetasks sections. I then iterate backwards through the list, figuring that the active job or task is among the last ones in the list, until I find one whose list of files contains the current DCR path.

There's got to be a more elegant solution, doesn't there?

Thanks, Dan

Obey the KISS principle and pass a parameter.

If you can not (or do not want to) modify ALL affected WFs, create a wrapper. To do that, copy a script with some other
name, check for the presence of (Job|Task)ID Parameter, process if present or propagate the call to the original (renamed)
script Copy if it isn't. (If I were you I would also use this questionable trick as a breather to gain time to identify and fix other WFs
but that's just me)

kaalraa

You know the options. The only thing remaining on your part is to decide. Smiley Happy

)

I know that the job id and the task id are passed implicitly to scripts called from an externaltask, but is there an easy way to derive those values from a TPL script called from the script called from an externaltask? For some reason, iwgetfilejobs is not returning any values, even when run from the command line.

My first thought, after discovering that iwgetfilejobs would be no help, was to simply pass the values as arguments to the called script, but this externaltask script is used by several different workflows to call TPL files, so they would all need to be retrofitted.

My current clunky solution is to run iwgetwfobj and extract either the activeworkflows or activetasks sections. I then iterate backwards through the list, figuring that the active job or task is among the last ones in the list, until I find one whose list of files contains the current DCR path.

There's got to be a more elegant solution, doesn't there?

Thanks, Dan