Creating an operator ID

Create a new operator ID data instance by clicking Create > Organization > Operator ID.

Key parts

An Operator ID data instance has a single key part:

Field Description
Operator ID Enter a unique identifier. By convention, use the format of an Internet email address. For example, if Patricia works at Thorr, enter [email protected]. Walter Scafi at Markus Bank in the United Kingdom can be identified by [email protected]. The Operator ID need not match a person's email address. You can use another permanent identifier used within your company.

Naming convention guidance:

  • In addition to letters and digits, the identifier can include the following characters: period, single quote, tilde(~), underscore, exclamation point (!), ampersand (&), octothorpe (#) and no more than one @ character. Don't use forward slash or backslash characters in the identifier.
  • If the Security Policies feature (on the System Settings landing page) is enabled, enter an identifier that is at least as long as required by that feature. See Systems category — Settings landing page.
  • As a best practice, use the organization name (the key to an Organization data instance) as a suffix in Operator IDs.
  • An Operator ID can be up to 65 characters long.
  • Special processing applies to any user identifier that starts with the word External. Use such identifiers only to define external operators, those who use directed Web access for one-time processing of assignments.
  • Do not use system as an Operator ID name. This name is reserved, as it is used by agents.
  • Do not use pyBulkProcessing as a work queue name. This value is reserved for background bulk processing.
Note: After a requestor logs in, the Operator ID identifier is available on the pxRequestor page as the pxUserIdentifier property.
Short description This field does not make up the key parts for an Operator ID but is required to create the data instance. Enter a label for the operator that will appear on the form header.

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. For an example, search for "Bulk Operator Load" in the Pega Exchange area of Pega Community. You might need to adapt and extend this example to meet local requirements.

Adding an operator by using the Organizational Chart landing page

You can also create Operator ID data instances using the Operators and Organizational Chart tabs on the Organization landing page.

Note: The organizational chart is also available on the Organization, Division, and Organization Unit rule forms. To list operators associated with a node (identified in the Organizational Unit field on the Work Settings tab of the Operator ID instance), select the node, right-click, and select View Operators.
  1. Click Configure > Org & Security > Organization > Organizational Chart to display the chart.
  2. Select any node within the organization.
  3. Right-click to open the pop-up panel and click Add Operator. A pop-up window appears. The organization, department, or unit values are automatically filled depending upon which node you choose.
  4. Select missing organization information. Enter an operator ID, password, and full name. Select the operator's access group. All values are required.
  5. Click OK to create the operator ID instance.
  6. Open the Operator ID instance to add or modify the information. Some values such as work group and calendar are copied from a data transform.