After Routing the case to another work list, one copy remaining in my work list.
I have a parent case , where I am having a drop down list of users. If I select the value from that drop down list, at the submit of the case a new sub case will get created and the entire parent case (with the newly created child case) will be assigned to that selected user work list. I have used work-.Reassign activity. But what is happening is the parent case got moved to selected users work list. But I can see the same parent case in my work list as well. Also upon opening the parent case in the routed work list it says, "The flow this assignment corresponds to is no longer at this task".
Do we need to delete the old case from my work list manually? Can any one help me debugging the issue?
Could you explain me, what do you mean by old cases here? If you have altered the flow rule or added a new assignment or routing configuration. Please make sure that there is a complete path for older cases which are created before alteration, by the path I mean to say that older work object should have the sequence of assignments/other shapes leading to resolution state of that flow.
Currently, I am (User 1) owning the work object (say for eg. H-1234) and I am creating the child case(say for eg. C-1). Till this point it is working fine. Now I have a requirement to route the work object to some other user (say for eg. User 2). So for this I am using the Work-Reassign activity method followed by obj-save and commit methods. As a result I am able to see the work object (H-1234) in the routed user's work list (User 2). But I can also see the same work object (H-1234) in my work list (User 1) as well. while opening the assignment in routed user's work list (User 2), I am getting the below error message.
"The flow this assignment corresponds to is no longer at this task".
So my question is do we need to explicitly delete the work object from the source work list (User 1)?