Skip to main content

Creating an operator ID

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

Provide users with access to your application by creating operator IDs. When you create an operator ID, you can specify the background and general information about the user, define application access, and configure password credentials for the user.

For example, in a banking application, create operator IDs for customer service representatives (CSRs) who review loan requests, and the manager to whom the CSRs report.
Before you begin: To create an operator ID, you must have the pxCanManageUsers privilege, which is part of the PegaRULES:SecurityAdministrator role.
  1. In the header of Dev Studio, click Create Organization Operator ID .

  2. In the Short description field, enter the full name of the new operator.

    The value that you enter populates the Full name field in the operator contact information on the Work tab. The maximum length of the description is 64 characters.
  3. In the Operator ID field, enter a unique identifier.

    When you enter the identifier, consider the following guidelines:
    • 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 at (@) character. Avoid using the forward slash (/) or backslash (\) characters in the identifier.
    • An operator ID can consist of a maximum of 128 characters.
    • Special processing applies to any user identifier that begins with the word External. Use such identifiers only when defining external operators that use Directed Web Access (DWA) for one-time processing of assignments.
    • Avoid using system as an operator ID name. This term is reserved and refers to agents.
  4. Click Create and open.

    Note: The operator rule form is displayed on the page and you can continue to add information about the user. For example, you can configure access settings or provide organizational information.
Note:

Defining work routing settings for an operator

For continuous and efficient workload management and routing, define skills, work groups, and work queues for operators. As a result, an operator can receive work based on skill set and team membership. For reporting purposes and advanced routing use cases, configure the reporting structure.

For example, when you define the reporting manager of an operator, the manager might receive notifications about the operator's progress on a case.
Before you begin: Create an operator so that a user can access your application. For more information, see Creating an operator ID or Adding an operator by using the organizational chart.

Every operator has a unique worklist that accumulates tasks that the specific operator can retrieve. Additionally, an operator can access a work queue that collects tasks for a team to which the operator belongs. Any team member can pick up tasks from a work queue. Another name for a team is a work group.

For an automated selection of tasks to process, operators can use the Get Next Work logic. Get Next Work automatically prompts users with an assignment that currently has the highest urgency in work queues and work groups that the operator can access.

  1. In the header of Dev Studio, click Configure Org & Security Organization Operators .

  2. On the Operators tab, select an operator that you want to edit.

    Note: To find your operator faster, in the Search Text field, enter the operator name, and then click Search.
  3. On the Work tab, in the Organizational unit section, define the affiliation of the operator within the organization by clicking Update, and then provide a relevant organization, division, and unit.

    For example: For an organization, enter the name of your company, for example, UPlusTelco, and then provide a division and unit, such as BankingOperations for a division and Mortgages for a unit.
  4. In the Team field, enter a work group to which the user belongs.

    A work group defines routing of tasks and a reporting manager of the user.
    For example: If you create Team A to review mortgage requests and Team B to investigate issues with mortgage operations, the two teams can use separate areas of your application so that the work is logically separated.
  5. Optional:

    To assign a user to multiple work groups, click Add a work group, in the text box enter a work group, and then select the radio button next to the work group that you want to set as the default.

  6. Optional:

    To enhance the reporting options of your application, in the Reports to field, enter the reporting manager for the user.

  7. Optional:

    To enable routing of tasks based on a skillset, in the Skill field, enter the ability of the user, and then in the Rating field, enter the level of the ability.

    You can apply a rating from 1 to 10, where 10 implies the highest level of the skill.
    For example: To indicate that a user is a fluent speaker of French, in the Skill field, enter French, and then in the Rating field, enter 10.
  8. Optional:

    To allow the user to process assignments from a work queue that corresponds with the user's work group, in the Work queue section, click Add item, and then provide a work queue and an urgency threshold.

    During Get Next Work processing, your application ignores assignments with urgency lower than the urgency threshold. For more information about Get Next Work, see Customizing the Get Next Work logic.
  9. Optional:

    To assign the user to multiple work queues, click Add item, and then repeat step 8.

  10. Optional:

    To trigger the Get Next Work algorithm to retrieve assignments from the work queues of the user first, select the Get from work queues first check box.

    Otherwise, Get Next Work picks up the top assignment on the user worklist, and accesses work queues only if this user's worklist is empty.
    For example: If a user is a member of the Team A to review mortgage requests, the Next Get Work algorithm suggests assignments that the application routes to the Team A work queue first and then moves to the assignments from the user's individual worklist.
  11. Optional:

    To trigger the Get Next Work algorithm to retrieve assignments from all work queues that correspond with the team that you provided in step 4, select the Use all work queue assignments in user's team check box.

  12. Optional:

    To trigger the Next Assignment item to consolidate assignments from all of the work queues of the user, sort by assignment urgency, and return the most urgent assignment in any work queue, select the Merge work queues check box.

    If you select the Use all work queue assignments in user's team check box in step 11, the system selects the Merge work queues check box by default and you cannot clear this check box.
  13. Click Save.

Defining operator availability

Ensure that the workflow in your organization is uninterrupted by defining operator availability and substituting operators that can receive work when the operator is unavailable. As a result, you ensure that the processing of your business cases continues even when some of the users are unavailable to perform work.

  1. In the header of Dev Studio, click Configure Org & Security Organization Operators .

  2. On the Operators tab, select an operator that you want to edit.

    Note: To find your operator faster, in the Search Text field, enter the operator name, and then click Search.
  3. Optional:

    To allow applications to route additional assignments to the worklist of the user that the operator ID identifies, on the Work tab, in the Availability section, select the Operator is available to receive work check box.

    If you leave the check box cleared, the operator can log in, enter work items, or complete assignments that are already in the worklist. The operator can receive work from other operators and from a manager.
  4. Optional:

    To define the working days and national holidays for the operator, in the Business Calendar field, select the relevant calendar.

    For example: Enter USDefault.
  5. If the operator might be unavailable in the future, in the Scheduled absences section, in the Unavailable form and To from, define a time period during which the operator is unavailable to perform work.

    For example: If the operator has a scheduled medical leave between January 1 and January 15, select the relevant dates.
  6. Optional:

    To define more periods of unavailability for an operator, click Add item, and then repeat step 5.

  7. Optional:

    To define how an application routes work when the operator is unavailable, in the When unavailable section, in the Substitute operator type list, select who or what work queue receives work:

    • To route work to another operator, select Operator.
    • To route work to a list of assignments for a team, select Work queue.
  8. Optional:

    To determine a substitute for the unavailable operator at run time, in the Decision tree to find substitute field, enter a decision tree that evaluates conditions and finds another assignee for the assignment.

    Based on your configuration in step 7, select a decision tree that returns either an operator ID or a work queue.
  9. To identify the operator ID or work queue name of a substitute for new assignments that an application routes to the unavailable operator, enter a relevant value in the Default to assignee field:

    • To route work to a specific user, enter the operator ID of the user.
    • To route work to a team's list of assignments, enter the work queue.
  10. Click Save.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice