Previious task id

Is there and function availabel for which we can find the previous task id in an external task. One way is to get it from iwgetwfobj command, but is there any other way for it.

Find more posts tagged with

Comments

ISCBorisB

Is there and function availabel for which we can find the previous task id in an external task

OOTB there is no such function. You'd have to code it.

If you have single possible Predecessor you can perhaps get a Task Object using WFworkflow::GetTaskByName
and then WFtask::GetId.

For multiple Predecessors you can set up this information yourself in the predecessor task(s) so that required task can
access it. Use "wfvarfinishop" attribute of the user/group tasks to set the callback value for the (following) external task.

Finally, you can get and parse Workflow objects, as raw XML or with (some) help from TeamSite::WFutils.
Note that it's neither trivial nor documented/supported by IWOV.

Adam Stoller

OOTB there is no such function. You'd have to code it.

If you have single possible Predecessor you can perhaps get a Task Object using WFworkflow::GetTaskByName
and then WFtask::GetId.

For multiple Predecessors you can set up this information yourself in the predecessor task(s) so that required task can
access it. Use "wfvarfinishop" attribute of the user/group tasks to set the callback value for the (following) external task.

The wfvarstartop and wfvarfinishop are, IMO, often overlooked but useful parts of the workflow design - you can easily use them to set the value of a variable (e.g.: "last_task") to the name of the current task using "%task" - and then, as indicated above - reference the same variable from the next task in line (assuming it is a script-oriented task type) to find out which task transitioned to it (using the information in the first previous paragraph above to get the ID of the task [if needed])

Finally, you can get and parse Workflow objects, as raw XML or with (some) help from TeamSite::WFutils.
Note that it's neither trivial nor documented/supported by IWOV.

Another possible method - which I haven't tried so cannot verify - is to use TeamSite::WFtask's GetComments() method which returns an array of hash references that include the task information (I believe name, though it might be id) - and through a little examination you should be able to figure out whether the first, or last, element in the array has the task information you're looking for. Again, I haven't tried this, and it's clearly not what it was intended for - but it might work.

Adam Stoller

The wfvarstartop and wfvarfinishop are, IMO, often overlooked but useful parts of the workflow design - you can easily use them to set the value of a variable (e.g.: "last_task") to the name of the current task using "%task" - and then, as indicated above - reference the same variable from the next task in line (assuming it is a script-oriented task type) to find out which task transitioned to it (using the information in the first previous paragraph above to get the ID of the task [if needed])

FYI - I realize now that I misread part of the documentation - the '%task" magic variable only works for the eastartop and eafinishop directives - not the wfvarstartop and wfvarfinishop directives - so if you use the wfvar* directives for this purpose you need to make sure that you explicitly set the value to the name of the task correctly.