Question
Get Error Message "The flow this assignment corresponds to has been removed." while reopen a work object
I get this specific error message: "The flow this assignment corresponds to has been removed." while reopen a work object. I try to reopen a work object via wrapper activity which starts with flow-new the reopen flow. After calling a flow action with the same name I get the named error message. I try to analyse the problem with the tracer and I see, that the pyWorkPage and also pxFlow of the work object is deleted by WorkUnlock. Do any bad configurations lead to this problem?
Hello,
I use a custom activity to start a flow. The flow is needed because of a flow action, which holds a section for choosing new values for the restarted work object. I can't call a flow action without an assignment and that's the reason for this solution. After the flow is started the pyWorkPage of the work object exists and holds pxFlow with a new entry. The pyWorkPage is deleted while starting the flow action and after finnishing the assignment.
Hi Matthias,
I'm not clearly understanding your issue to be fully honest. Have you try with the default Work-.Reopen ? Do you still have the same issue.
Hi Marc,
I use the default Work-.Reopen activity and I still get the named error message.
Is the flow that the WO followed when it initially existed and was resolved the same as the one it will follow once it is reopened?
Refer to the following from OpenAndLockWork activity:
ClipboardProperty flowRef = myStepPage.getIfPresent(".pxFlow(" + flowSubscript + ")");
if (flowRef != null)
{
...
...
}
else
{
tools.putParamValue("SuccessIndicator", "-22");
tools.putParamValue("FailureInfo", tools.getRuleMessage("OpenAndLockWork-FlowRemoved"));
tools.putParamValue("FailureMsgDesc", "ProblemAssignment_FlowRemoved");
}
It is not the same flow. I define a new one for changing a property in the restarted work object. After that the original flow is started by a post activity.
Accepted Solution
Well , I think you need to refer to the same old flow in order to make it work properly.
If you really need to refer a different flow for reopen cases then, you can try the following
1. Launch the old flow on click of reopen
2. Then use a decision shape in this flow and move the control to a subprocess ( your new flow ) based on whether it is a reopen candidate or not.
Let me know whether this works or not.
Hello,
Which wrapper activity are you using ? A custom one or an existing one ? Can you try with the default Work-.Reopen ?
I guess if the case is closed, on the pyWorkPage, you shouldn't have anything on pxFlow page which is normal. I'm not sure why the WorkUnlock would be called here, I would expect the WorkLock one instead. Can you share your trace ?