Imagine social networking sites. They have a Sign Up link in their home page. You can sign up to create a new account. “What happens at the back end?“. A new account is created for you and it is stored in the server.
Username will be the key to link the account. So whenever you login again, the application will match your UserID and get the details related to your account.
Now, let’s come to our Pega application. As like other applications, we need a Login ID to access Pega application.
Technically Login ID is called as “Operator ID“.
What is an OperatorID?
- It is a rule which comes under Organization category.
- It is a unique ID for each individual users.
- It is an instance of Data-Admin-Operator-ID. It means whenever you create a new operator ID, a new instance of class Data-Admin-Operator-ID is created.
Note: Data-Admin-Operator-ID is mapped to pr_Operators table. So whenever you create a new operator ID, you can see a new entry is made into pr_Operators table.
How do we configure an OperatorID?
Whenever you install Pega, you will have an administrator Operator ID. You can login and configure the administration settings. – administrator@
1. While creating a new application
Try creating a new Framework application and preview the records.
2. SSO Authentication activities
- In Production, we always use SSO for Login.
- SSO – Single Sign On. It provides a facility to login once and access all applications securely.
Say, “You logged in your office desktop using organization credentials. If SSO is enable in Pega, then you can directly access Pega”. It is not necessary to have operatorID in Pega for SSO. Also SSO authentication activities can create new Operator IDs.
This is beyond the scope of this post. I just wanted to let you know OperatorID can be created via SSO authentication activities.
3. Manual creation
This is the normal case where team lead creates new Operator IDs for the developers.
- Create a new operator ID from Operator ID -> right click create new.
There are 3 main tabs:
Contact Information – Fill out the basic contact details of the Operator ID.
Application Access – You can specify ‘n’ number of access groups for an Operator ID, but remember only one can be active at a time.
Check the Radio button to select default access group.
What is Localization?
- Localization supports accessing the same application in different regions. We know different regions use different languages, date formats. Localization is possible in Pega.
- You can specify to which localization should this operator belong to.
- You can leave this empty.
For IE, normally the localization applies for all sites based on the below settings.
This can be overridden in Pega application when we use Localization. We will discuss it later in different lesson.
Routing – You can associate all the routing parameters with the Operator ID.
a) Organizational Unit – You can update the Organization / Division / Unit, the operator belongs to.
b) Work Group – You can specify the work group the user belongs to.
As the name suggests, it is simply a group of people related by their work. Each workgroup contains a manager.
c) Reports to – You can specify a Operator ID here. The property .pyReportTo holds the value.
d) Skill – You can specify a skill rule here.
e) Rating – Specify a value between 1-10.
This is mainly used for routing purpose. Imagine in a call center application, for premium customers you may need the most skilled call center agents to contact them. You can specify those skill and ratings here.
The below part in routing, belongs to GetNextWork.
What is GetNextWork?
- It is simply a button on a user portal. When you click it, it displays a new assignment for you to work.
- This can pull assignments either from your worklist or workbasket.
Imagine when there are no items available in work list, the user can click on GetNextWork to pull a new assignment to work. It pulls the assignments from workbasket the user belongs to.
You can think users can manually pick work items from the workbasket. Yes, they can, but there are chances that he/she may pick irrelevant items. To avoid this Pega provides GetNextWork functionality to pick the item.
We will see GetNextWork in separate lesson.
Workbasket – You can specify as many workbaskets as you want. Remember this does not restrict users from accessing other workbaskets.
Operator is available to receive work – Check this to make the operator receive work through router activities.
Note: Activity of type router checks a parameter (this parameter) first before routing the assignments to his/her worklist. If this is unchecked, then the assignments get routed to substitute operator/Manager.
Get From workbaskets First –
True – GetNextWork checks the assignment from workbasket first, and then only it checks the worklist.
False – GetNextWork checks the assignment from worklist first, and then it checks the workbasket.
Merge Workbaskets –
True – The order of workbasket array listed above is not important. GetNextWork assembles all the assignments from the workbaskets and pick a most relevant item.
False – The order of workbasket array listed above is important. GetNextWork first checks the assignment from the first workbasket. If no assignments are found, then it checks the second and goes on.
Use all workbasket assignments in User’s workgroup – visible when merge workbaskets is true.
GetNextWork assembles all the assignments from the workbaskets which belongs to Operator workgroup.
Note: Each workbasket belongs to a workgroup.
Scheduling – Records the future scheduled absences. Standard routing activity uses these values.
You can specify substitute operators here.
a) Time Zone – Specify a time zone. This is not mandatory. You can leave this blank, if you want the operator to follow the Organization time zone.
b) Calendar – Specify the calendar rule. This is not mandatory. You can leave this blank, if you want the operator to follow the Organization time zone.
c) Unavailable From To – You can update the date range in which the operator is unavailable to receive work.
You have an option to add more than one time range.
Substitute operator configurations
d) Substitute Operator type – The substitute operator can be either Operator or workbasket.
e) Decision tree to find substitute – You can specify a decision tree, if you have a complex logic to find the substitute.
f) Default to assignee – You can specify either an Operator or a Workbasket name here.
a) Update password – You can update the operator password here.
b) Allow rule checkout – If enabled, you can Checkout or private edit the rules. Restore options are available when you enable it.
c) Use external authentication –
True – Authentication is based on LDAP / SSO.
False – Used Pega operator ID password.
d) Starting activity to execute – Data.Portal.ShowDesktop
This is a defaultOOTB activity. You can use it as such.
e) License Type –
Named – For operator ID instances accessing through web browsers – default value.
Invocation – This Operator ID is used for processing service calls. We use it rarely.
Important Points to note down:
- On completing the rule form and saving creates a new entry to PR_Operators table.
- PR_Operators table contains many columns like ‘pyUserIdentifier, ’pyAccessGroup’ etc., which contains the details regarding the operator ID.
- Use Live UI on the Operator rule form and check various fields in Operator ID form.
You can see Email address gets saved in a pagegroup property.
You can see pyReportTo property.
All these properties get saved as separate columns in PR_Operators table.
- You can check all the Operator ID details in clipboard system pages.
We shall verify the email address we provided in the Operator rule form.
Hope you are clear with the basics 🙂
Next posts will be on Authorization rules – Access group, roles, ARO and privileges (hhttp://myknowpega.com/2017/05/15/67/) , 🙂