Back Forward Operator ID data instances
Completing the New or Save As form

About Operator ID data instances

 zzz Show all 

An operator ID data instance has a single key part. You can add Operator ID data instances through the  New toolbar button (New), or the Organization Chart facility.

 zzz1. Starting the process

Method 1: Adding an Operator ID from the toolbar

This approach provides access to every field in the Operator ID form.

  1. Click the New button (New) on the Developer portal toolbar.
  2. For the Type field, select Operator ID from the Organization category.
  3. Complete the Operator ID field.

Method 2: Adding an Operator ID with the New button

The New button provides access to every field in the Operator ID form.

  1. Select View > Organization > Operators.
  2. Click the  New   button.

Method 3: Adding an Operator ID with the File > New menu

A faster approach is available if the new operator is to belong to the same organization unit as yourself.

  1. Select File > New > Operator to add an operator to your organization unit.
  2. Enter an e-mail address, name, Operator ID, password, and access group for the new operator.
  3. Choose an Operator Type of Worker, Manager, or Developer.
  4. Click  Create  .
  5. Other values for the new Operator ID data instance are copied from a model. Open the Operator ID form and update the values as required.

Method 4: Adding an Operator ID with the Organization Chart

To use the Organization Chart facility:

  1. Select View > Organization > Organization Chart to display the organization chart, or access the Chart tab on the Organization, Division, or Organization Unit form.
  2. On the chart, select a 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. In this example, the division named Administration was selected.

  1. In the pop-up window, use SmartPrompt() to select the organization information (unit name in this example) and access group. Enter an operator ID, password, and full name. All values are required. (If your own RuleSet list contains the optional PegaPwdControl RuleSet, choose a password value that meets the criteria defined in this RuleSet.)
  2. Click  OK   to create the operator ID instance.
  3. Open the operator ID rule form to add or modify the information. Some values such as work group and calendar are copied from a model.

While in the chart, you can click the Open option to display a list view of operators and select the new operator ID from the list.

 zzz2. Completing the Operator ID key

Field

Description

Operator ID

Enter a unique identifier. By convention, use the format of an Internet e-mail 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 e-mail address. You can use another permanent identifier used within your company.

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.

After a requestor logs in, this identifier is available on the pxRequestor page as the pxUserIdentifier property.

Tip As a best practice, use the organization name (the key to an Organization data instance) as a suffix in Operator IDs.

NoteAn Operator ID may be up to 128 characters long.

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

NoteYou can't use system as an Operator ID name. This name is reserved, as it is used by agents. Also, you can't use pyBulkProcessing as a workbasket name. This value is reserved for background bulk processing.

zzz About Operator ID data instances