Close popover

Table of Contents

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.

  • Enabling and disabling operators

    You can control which users can access your application or are authorized to work on assignments in your application. By providing the minimum level of access that each user requires, you can improve the security of your application.

  • Understanding Requestor Type data instances

    Users and external systems connect to Pega Platform using one of four requestor types. Requestor type data instances define the types of requestors that can access your system, such as a browser session, an external application, or an internal background process.

  • 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.

  • Fields for operator contact information and application access

    Complete the Profile tab to define the contact information, application access, and localization information for an operator. The access groups that you specify affect which rulesets, ruleset versions, and portals the user can access.

  • Fields for operator teams, work queues, and schedules

    Use the Work tab to identify the skills, teams, work queues, and work schedule for an operator. The work queues are searched for assignments when users click Next assignment on the Case Manager portal.

  • Access When form — Advanced tab

    For complex conditions, use this tab to enter conditions and a logic statement that combines them.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.