We are currently building in Pega Constellation and have run into a UX friction point regarding how users transfer assignments.
Under the current out-of-the-box behavior, if a user wants to transfer an assignment to another person or work queue, they must go through a multi-step process:
Click and open the specific assignment.
Open the three-dots (More Options) menu.
Select the “Transfer Assignment” local action (pyTransferAssignment).
This process is click-heavy and cumbersome, especially for users whose primary role involves triaging or reassigning work.
My Questions:
Is there a recommended way or best practice in Constellation to streamline this?
Is possible to transfer any assignment without opening it ?
Any guidance, alternative UI patterns, or workarounds would be highly appreciated.
This is by design because pyTransferAssignment operates on the current assignment (newAssign page), which is only available once the assignment is opened.
If your users spend most of their day triaging work, the best user experience is to add a custom row-level action such as Transfer directly on the assignment list.
The implementation would typically:
Add a “Transfer” action/icon on each assignment row.
Invoke a custom DX API or custom case action.
Perform the assignment reassignment in the backend.
Refresh the assignment list.
This will reduce interaction from 3-4 clicks to a single click plus destination selection while keeping users on the worklist.
You can also try implementing a bulk transfer feature as a custom enhancement. I believe there are knowledge documents already available for this on pega forums for Constellation
Hi, bulk actions are not natively available on assignments (we have them on cases) but there is a way to implement it. Please read this article: Constellation Tips: Bulk Transfer Assignment
