Requirement: After a certain stageprocess, the flow has to wait until a specific date before assigning it back to the user.
How did we do this?
in the process, we’ve added a wait step with routing to [email protected] in order to wait for a specific date to pass. Once it’s passed, the flow should continue into the next assignment
the following assignement was originaly routed to “current Operator”, but I read somewhere this wasn’t ok as the current operator is the Agent (is this true?)
Now I’ve replaced the routing of the next assignment to the “[email protected]” worklist, but the user still can’t continue to work on the assignment.
If you want to assign to it to the user, you can add that user as a workparty to your case. Once the flow is resumed from wait shape you can get the details for the assignment from the workparty page.
The problem is in routing configuration. What you have mentioned is correct, after wait shape time is getting completed, system agent will be resuming the case from wait assignment to get process further. Agent is not an operator/user, so you would not be able to use Current Operator for wait shape next assignment routing.
For achieving this requirement what you could do is,
If in case you would need to route the case to same user who have worked on the same work object already after the wait is completed, then you could initialize the user who have been worked on case already as a work party and you could use work party based routing in the assignment which you will be having next to wait shape.
If in case you need to dynamically find the user to whom the case needs to be routed after wait shape is completed and route the task. Then you could create application specific routing activity and inside routing activity you could build your logic to find the user to whom the task needs to be routed.
@Gunasekaran_Baskaran but in that case back to back assignment isn’t gonna work anymore. Any idea how it possible to make with back to back processing?