Question
Bank of America
IN
Last activity: 7 Jun 2024 2:07 EDT
Screen flow with different assignies
Im using screen flow which has 8 screens out of which employee enter input for 1st 5 steps and 6th and 7th screen has to input by Manger and remaining 8th screen its should route to User again. how can we implement this scenario
Accepted Solution
Updated: 7 Jun 2024 2:07 EDT
Eclatprime Digital Private Limited
IN
Hello, while transferring the assignment set the below fields and post this, it would route all the assignments to newly routed user.
need to reset pxFlow properties
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.
Hope this helps.
Thank you.
TSPi
US
Eclatprime Digital Private Limited
AU
In Pega, the nature of screen flows is such that they are intended for use by a single operator to complete a series of steps sequentially without changing the operator in the middle of the flow. This is because screen flows are designed to provide a seamless user experience where one user can complete all steps without interruption or reassignment.
No Routing option available on assignment shape to route other user in screen flow
Key Points About Screen Flows and Routing in Pega:
-
Single User Interaction:
- Screen flows are designed for single-user interaction to maintain continuity and context. This ensures that the user maintains the state and context of the process throughout the series of screens.
-
Session Persistence:
- Screen flows keep the session and clipboard data consistent for the user. If the flow were to switch users, it could disrupt the continuity and lead to potential data consistency issues.
-
Simplified User Experience:
In Pega, the nature of screen flows is such that they are intended for use by a single operator to complete a series of steps sequentially without changing the operator in the middle of the flow. This is because screen flows are designed to provide a seamless user experience where one user can complete all steps without interruption or reassignment.
No Routing option available on assignment shape to route other user in screen flow
Key Points About Screen Flows and Routing in Pega:
-
Single User Interaction:
- Screen flows are designed for single-user interaction to maintain continuity and context. This ensures that the user maintains the state and context of the process throughout the series of screens.
-
Session Persistence:
- Screen flows keep the session and clipboard data consistent for the user. If the flow were to switch users, it could disrupt the continuity and lead to potential data consistency issues.
-
Simplified User Experience:
- The primary goal of a screen flow is to simplify the user experience by allowing one user to navigate through multiple screens (steps).
-
Design Limitation:
- By design, Pega enforces that screen flows are not meant for multi-user interactions within the same flow instance. Assignments within screen flows cannot be routed to different users because the flow expects the same user to complete all steps.
For your scenerio sloution:-
In that stage add two screen flows and one screen flow for employee and other screen flow for manager. Oherwise add the standard process flow add route the each assignment any user you need.
Accepted Solution
Updated: 7 Jun 2024 2:07 EDT
Eclatprime Digital Private Limited
IN
Hello, while transferring the assignment set the below fields and post this, it would route all the assignments to newly routed user.
need to reset pxFlow properties
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.
Hope this helps.
Thank you.