Posted: 1 Feb 2018 10:46 EST Last activity: 14 Feb 2018 6:12 EST
OOTB for retrieving operator information based on operator id
I am new to Pega. We are trying to automate case creations in pega using service HTTP rule; during which we are currently hardcoding the operator information. Instead, we are thinking of passing the operator id and then identify the operatory name (for the passed operator id) and assign this to the case.
Is there a (OOTB) method to retrieve the operator information based on a operator id? If there isn't any OOTB method, can someone provide pointers to proceed with the implementation. Appreciate your help.
For instance, information about each user (known as an Operator ID) of the system is saved as a row of the table named pr_operators. If your system has information for 340 users, this table has 340 rows. The column named pyOrganization contains the name of the organization that the user belongs to.Another column pxInsName contains the text value of the key to the row.You can fetch most of the details from this table.
Posted: 3 years ago
Posted: 2 Feb 2018 9:24 EST
Umamaheshwar Reddy Midthuru (Mahesh Midthuru)
Senior Software Solutions Engineer
You can have a look into Data-Admin-Operator-ID.pxGetOperatorDetails activity, which takes the operator id as parameter and uses Obj-Open method to get the OperatorID record from database into clipboard.
Hope this information might be helpful to you to construct your own activity or use this if its feasible to your requirement.
There is a linked property concept in Pega where this may help to achieve your requirement.
If you open Work-.pxCreateOperator property ,it is linked to Data-Admin-Operator-ID table and linked class key is pyUserIdentifier.The advantage of this feature is you need not open Operator record explicitly. You just need to simply set the value of pxCreateOperator in one step(in activity). Pega will automatically open the operator record . so you can easily access by pxCreateOperator.pyName etc...
You can see those records in linked properties section in clipboard page. The scope is with in your requestor so it exists till you log out.