Question
JPMC
US
Last activity: 17 Sep 2015 20:29 EDT
Information related to operators
I need to get following audit information for operators, Could you guys help me with approach:
1. User logged off/Passivation time
2. All deleted user ids?
3. All activity performed by an operator(including everything work history, rule updates, report runs etc.)
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Updated: 17 Sep 2015 3:24 EDT
Pegasystems Inc.
IN
The passivation timeout usually will be specified in prconfig.xml file by setting some of the flags where as authentication timeout is specified in the access group of the operator .
To get the information about the other two, the below pdn link may help .
https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
Pegasystems Inc.
FR
Also for your information, deleting OperatorID isn't recommended. On the same help file you can see this:
Deleting operators
PRPC does not prohibit deletion of an Operator ID instance 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).
If a user is no longer active, rather than deleting the Operator ID instance, you can follow these steps:
- Ensure that this user is not currently logged in.
- Transfer or complete all assignments on the worklist.
- Update the password to a value that is not disclosed to the user, so that person can no longer log in.
- Ensure that this user has no rules checked out. If not, sign on and delete or check in the checked-out rules.
- Clear the Operator is available to receive work? checkbox.
- Enter a departure date in the Unavailable from array.
- Enter a substitute operator for assignments routed to this operator.
- Save the updated Operator ID instance.
You can't delete an Operator ID if the operator has rules checked out. Have the operator sign in, and delete or check in all rules in the operator's personal RuleSet.
JPMC
US
Thank you Marc for the detailed step to properly decommission an operator from an application! but certain security requirements need an operator to be deleted/cleanup like when a user leave organization, moves from one LOB to another. we are planning to reassign any assigned work items to a workbasket.
JPMC
US
Thank you Haritha for your response! Actually for the first question I was looking for the timestamp when user logged off OR if not logged off then at what time it was passivated?
Thanks for the link. It seems an useful link if we want to track changes in certain data/rule instances which does not maintain specific changes but it doesn't seems give answer to my ques 2 & 3.
Pegasystems Inc.
US
Dhirendra,
As for your third ask... we don't track all of that OOTB. You can cobble some of it together from various reports of places like the history tables. That said, if you want to track things like every time a user runs a report, you will have to add that audit trail yourself.
Thanks,
Mike
JPMC
US
Thanks Mike! I knew there is no central place to get all these audit details but it would be really nice if we could add enhancement in future pega ML release to have a DB View which can give overall picture at one place, not sure how feasible and useful this would be in general.
What you are asking for seems like a nice enhancement to the product. Else you'll end up writing lot of custom code (with PS help) that might break when you upgrade.