Discussion

Commonwealth Bank of Australia (CBA)
IN
Last activity: 26 Sep 2025 0:07 EDT
Solving Screenflow Reassignment Issues in Pega: From Work Queue to Current Operator
Problem Statement
In a Pega application, a screenflow is configured with 5 assignment shapes (screens). The Start shape of the screenflow is routed to a work queue. When an operator picks up the case from the queue, they are able to open the first screen. However, upon submitting to the next screen (or navigating forward/backward), the case is automatically closed and reassigned back to the work queue.
This behavior forces the operator to reopen the assignment from the work queue every time they want to proceed to the next screen or navigate within the flow. This disrupts the user experience and slows down case processing.
The goal is to allow the operator to freely navigate forward/backward through the screenflow after picking up the case, without needing to reopen it from the work queue repeatedly.
Resolution
As mentioned in this Post :
https://support.pega.com/question/re-assign-screen-flow-another-user
while transferring the assignment set the below fields and post this, it would route all the assignments to newly routed user.
This fields can be set in the local action post processing activity which is transferring assignment. Note: after the updating the values these needs to be persisted onto pyworkpage.
- .pxFlow(flowName).pyFlowParameters.AssignTo = reassigning operator id
- .pxFlow(flowName).pyFlowParameters.DefaultAssignTo = reassigning operator id
flowName is the name of the screen flow on which routing is being changed, this can be fetched from newAssignPage.pxFlowName.
Along with this set :
.pxFlow(flowName).pyFlowParameters.SwitchToWorkbasket= false in order to assign to a user.
This can be done in the PerformDefaults Extension activity after Calling reassign Activity .