Question
Pegasystems Inc.
AU
Last activity: 18 Mar 2016 14:44 EDT
Can we delete Operator record when people leaving organization.
Hi there,
There is no option for me to disable the operator ID from accessing the system when people leave organization. I can reset the password, but ideally if I can delete the record, it would be good. However, I am not sure of the impact of deleting operator id... e.g. there might be existing work assignment etc.
Regards
Seri
Message was edited by: Lochan to add Category
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
What is the PRPC version you are making use of?
Pegasystems Inc.
AU
Client is on 717 (upgraded from 6.3)
Pegasystems Inc.
IN
Hi Seri,
Below is URL from Pega 7.1.7 help
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
Kindly close this thread if this answers your query.
Pegasystems Inc.
IN
You can refer "Deleting Operators' Section in below PRPC help url:
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
Updated: 17 Mar 2016 12:24 EDT
Process 360
IN
The helps says "Deletion of an Operator ID instance is allowed when there are open assignments on that operator's worklist, or when that Operator ID is referenced in another data instance (such as an organization unit or workbasket)."
I did not understand what it is trying to say. Sorry for my ignorance but can you please explain in detail.
Pegasystems Inc.
IN
I think this is documentation bug, ideally it should be:
"Deletion of an Operator ID instance is NOT allowed when there are open assignments on that operator's worklist, or when that Operator ID is referenced in another data instance (such as an organization unit or workbasket)."
Process 360
IN
Also the help is mentioning about the work around's / making an operator inactive but doesn't really say as to how to delete the operator.
Pegasystems Inc.
IN
Operator can be delete like other rules ( with no dependencies on a particular Operator id).
This link suggests that instead of deletion, it is best to make it void.
Hi Arvind,
Thank you for identifying the error in the Help document. We have created a BUG for the documentation team to evaluate.
Regards,
Lochan
Virtusa Pvt Ltd
US
Arvind shared link will be really useful. If your intention is to stop the user from accessing the system you can simply remove all the AG records from his operator id, then he won't be able to log into any of the portals.
Euroclear
BE
If you do not wish to have the operator in the application then you may choose to do the below steps :
1.As you are not supposed to delete an operator with open assignments , it is better to check if he has open assignment.
Execute the following SQL in your Data schema.Substitute the pc_work with the work table that your application uses and you may choose worklist or workbasket depending on
the type.
select a.pzinskey,b.pxtasklabel,b.pxtaskname from pc_work a ,pc_assign_worklist b where a.pzinskey=b.pxrefobjectkey
and b.pxassignedoperatorid='Richard';
Sample O/P :
If you do not wish to have the operator in the application then you may choose to do the below steps :
1.As you are not supposed to delete an operator with open assignments , it is better to check if he has open assignment.
Execute the following SQL in your Data schema.Substitute the pc_work with the work table that your application uses and you may choose worklist or workbasket depending on
the type.
select a.pzinskey,b.pxtasklabel,b.pxtaskname from pc_work a ,pc_assign_worklist b where a.pzinskey=b.pxrefobjectkey
and b.pxassignedoperatorid='Richard';
Sample O/P :
PZINSKEY | PXTASKLABEL | PXTASKNAME |
WORK P-106 | Campaign Suspended | Assignment2 |
WORK P-107 | Campaign Suspended | Assignment2 |
WORK P-156 | Pending Wrapup | ASSIGNMENT63 |
WORK P-157 | Pending Wrapup | ASSIGNMENT63 |
WORK P-158 | Pending Wrapup | ASSIGNMENT63 |
WORK P-160 | Pending Wrapup | ASSIGNMENT63 |
You will now get an idea about the open assignment the operator has.If there are no rows as o/p the go ahead and delete the operatorid instance.If there are open assignments (as above) , go to step no. 2
2)Write an adhoc activity to delete the open assignments.
1.Obj-Browse with the same query that i had mentioned in step 1.It will give you a pxResults page with pzinskey,pxtasklabel and pxtaskname.
2.Using the pzinskey open the work object instance using obj-open-by-handle for all the instance in the page list , set the status as Resolved-completed and do an obj-save.
3.Now you are good to delete the operator.