Hi,
There is a requirement to implement a screen flow with three screens and enable transfer of assignments when there is a need to move the case to another queue or user. However, we have observed a limitation: the case cannot be transferred while it is in a screen flow, as routing is only supported at the start of the flow.
It would be greatly appreciated if you could suggest a workaround to support assignment transfers in this scenario.
Screenflow designed so the flow can be completed by same user, you can’t send the case to another user or WB while working with screen flow. You need to look your design again if you need to transfer the case.
While screen flows are structurally designed to be executed end-to-end by a single user, you can technically force a transfer in exceptional scenarios (such as an operator suddenly becoming unavailable).
To do this, you need to update the routing references in both the assignment instance and the active flow metadata:
Update the Assign-Worklist instance to point to the new operator.
Update the corresponding pxFlow(FlowName) page on the case, specifically setting the new operator ID in:
.pyFlowParameters.AssignTo
.pyFlowParameters.DefaultAssignTo
Once these references are updated, the screen flow will successfully resume from that specific step for the new user. However, this should strictly be used as an administrative workaround rather than a core application design pattern.
As @MISHR said, screenflow assignments must be worked by the same user. If you’re expecting different users in the screenflow, then you may need to change the design. For exception scenarios, use TransferAssignment to route the users from one user to another user.