Open Assignments for an Operator being deleted
Pega validates Checked out rules when we delete operator and avoids deletion. Similarly it should validate any open Assignments before deletion. Does pega support this? If Not I feel this is a universal problem of Orphaned assignments, how are org handling these?
Updated: 25 Jun 2025 4:38 EDT
Freelancing
IN
@Arvind I see that it not automatically taken care in Pega as on today, but as an org we in the past followed the following steps / Best practice when any users or the Operator exit the application. 1) If the Operator is SSO or Local operator it's the role of Lead / Admin team to Disable the operator profile, this will ensure the access restrictions to the Portals.
2) Once step 1 is applied we can move the assignments to Work Basket or the Other worklist based on the need.
3) This option is bit different and is very specific to each client where we can automate this process and define the client specific rule to identify the operators who are inactive over a period of time and disable them automatically, transfer the assignment and later delete the operator eventually. Hope this provides some insights... Thanks Chandan
BNYMellon Technology
IN
@Chandan_U Thank You for the response.
Yes Disabling is an option and we can have a Job scheduler to move assignments of Disabled operator to a Workqueue and send notifications. But the problem is if someone leaves the org as part of the offboarding process, they are deleting the operator id same day. So We have to build something during the delete operation.