WF tasks disappearing!!

Hi All,

I am having a sction of the WF, where there are a number of user tasks being generated with the successors as "Approve" and "Reject". When any one of the user task is trasition to the "Reject" successor, all the other generated user tasks are disappearing altogether. But if any of the user tasks transition to "Approve" successor, the other generated user tasks are still active. I have the portion of the WF code as an attachment. Could any one help me on this?

Thanks,
Amaresh

Find more posts tagged with

Comments

nipper

Can you put your WF in debug mode and post the generated XML ? That is easier to work with sometimes.

Adam Stoller

Hi All,

I am having a sction of the WF, where there are a number of user tasks being generated with the successors as "Approve" and "Reject". When any one of the user task is trasition to the "Reject" successor, all the other generated user tasks are disappearing altogether. But if any of the user tasks transition to "Approve" successor, the other generated user tasks are still active. I have the portion of the WF code as an attachment. Could any one help me on this?

Thanks,
Amaresh

I somehow doubt that the code you posted is the actual workflow code that was being used at the time you experienced the behavior you're indicating.

In order for the WFT code to do what you're saying:

I don't see any of that there.

amaresh

Hi,

Thanks for the response. Here is the XML after running in the dedug mode. The inactive element is at the right place. Is it mandatory to have an active element?

Thanks,
Amaresh

ISCBorisB

Hi,

Thanks for the response. Here is the XML after running in the dedug mode. The inactive element is at the right place. Is it mandatory to have an active element?

Thanks,
Amaresh

WF with the specs you've attached can not possibly behave the way you had described it. Your concurrent Approval tasks
transition to the same "Decide_Process" upon both "Approve" and "Reject" action. Further, the code fragment
you've posted at the beginning can not possibly generate Specification posted later on, there are numerous
discrepancies.

I understand that you are probably debugging it and changing code back and forth with 50 Hz frequency. If you
expect help with certain issues however you may contemplate a bizarre idea of posting code that manifests these issues.

So, since what you've posted is of no help, here is some speculation for what it's worth:

- Your tasks did not "disappear", they became inactive. They became inactive because somewhere in the flow you've
transitioned to the task (High_Level_Clearance1 ?) that deliberately inactivated them.

- Activation, Inactivation and Reset elements are optional syntactically. In a branched concurrent workflows like the
one you are developing they are practically always needed in some tasks to ensure proper logical conditions
for (possibly repetitive) task transitions.