Best Practice to manage Operator IDs
Hello! Is there a best practice to manage Operator IDs in Pega 6.x and 7.1.x applications? Is there a documented approach to handling operator ids for when folks transfer departments or leave the company? I was told early on that it is not a good idea to delete Operator IDs because you lose the operator ID information/references. My security department wants to delete operator ids due to security concerns. In the meantime, I have removed access groups to "disable" users.
Should we delete operator ids in production and QA, but keep them in development? What happens if an operator id is tied work items or workbaskets and they get deleted?
I know in Pega7.2.2, operator ids can be "disabled", which should suffice security.
Thanks!
***Moderator Edit: Vidyaranjan | Updated Categories***
Cognizant Technology Solution
US
While transferring department I think changing Access Group would work. But an approach to make sure that the Work Objects are not lost can be to write a utility for deleting/changing the Operator Ids and from the same utility call pxTransferWork activity first to transfer all works assigned to the Operator to a Work Basket so that other existing operators can work on that particular assignments.
Pegasystems Inc.
IN
- Transfer the operator's work cases before deleting the operator record. If the operator is deleted and there are cases for them, add the operator record back, transfer the cases, and delete the record again.
- Remove the privileges and access roles, so that the operator cannot be used, but they still exist and the cases can be transferred, and delete the operators.
This link may help you.
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm