Learning about operators
An operator defines a unique identifier, password, preferences, and personal information for a user. Create operators so that people and processes can access your application.
Clusters and operator IDs
After you save a new or updated operator ID instance, the change might not be reflected on another node in a cluster until the Pega-RULES agent on that node performs the next system pulse — typically after no more than 60 seconds. Unlike instances of most other Data- classes, the system saves operator ID instances to the rule cache. As a result, until the next time the rule cache is synchronized, one node might access a stale copy from its rules cache.
Bulk operator load
You can create operator ID instances by importing a comma-separated values (CSV) file, such as created by Microsoft Excel. You might need to adapt and extend this example to meet local requirements.
Operator ID property
After a requestor logs in, the operator ID identifier is available on the
pxRequestor page as the pxUserIdentifier property.
Operator IDs and external identity providers
If you implement authentication by using an external identity provider (IdP), the login process accesses IdP for authentication and ignores the password in this operator ID instance. However, an operator ID data instance is still needed for each user.
Operator passwords
Operator ID passwords are saved as hashed values in the PegaRULES database, using the salted bcrypt (default) algorithm. Two property types are used when changing the password, Password type for the New Password field, and Text type for the Confirm Password field. The Data-Admin-Operator-ID.pyPwdCurrent property stores the hashed password after it is validated.
On Pega Community, see Using the bcrypt hashing algorithm for Password property types for more information about the Password property type.
- Creating operator IDs
When you create an operator ID in Pega Platform, you set up a unique account so that a user can access the system. By creating an operator ID you can set the identifying information of the user, define their access rights, and configure password settings. You can also add additional details, such as their skills, to ensure that work is routed to the user based on their capabilities.
- Defining operator contact information and application access
Define an operator's contact information, application access, and localization information so that operators can be communicated with and can access the required applications. The access groups that you specify affect which rulesets, ruleset versions, and portals the operator can access.
- Defining operator work groups, work queues, and schedules
Define an operator's skills, work groups, work queues, and work schedule so that work can be assigned to operators who are skilled and available. The work queues are searched for assignments when users click Next assignment on the Case Manager portal.
- Defining security information for an operator
Use the Security tab to manage operator authentication, passwords, and license type, to allow rule check out, and to enable and disable the operator.
- Deleting operators
To ensure that only designated workers can access your application, you can disable access for users that are no longer active, for example, when they no longer work in your organization.
Previous topic Understanding project roles and personas Next topic Creating operator IDs