I took a workflow which was working just fine, added a CGITASK as one of the steps and now I am noticing some weirdness.
The task is intended to kick off, performs Task A, transitions to Task B (which is my new CGITASK), and is supposed to transition to Task C, D, E and then finish up. What actually happens is the following:
Task A is kicked off and completes.
Task A transitions to Task B.
Task B (CGITASK) is executed, however Task A is still on the TO DO list.
While Task B transitions to Task C, Tasks A and B are taken off the TO DO list, leaving Task C there by itself, which is expected.
After Task C completes, it does not appear to transition properly. What I'm left with here is Task C remains in the TO DO list with the only option to TAKE BACK the task.
With the exceptions of applicable successors and the inclusion of the new CGITASK, I have not touched the workflow at all and have intuitively copied the TRANSITION code from other CGITASKs, although I certainly may have missed something.
Does this problem sound familiar and could someone please point me in the right direction? I will gladly post the code if you want more specifics. Thanks in advance,
Dave
dave@simpleinternet.com+USA (215) 962-5153
