The system does not constrain team membership based on organization structure. Members of a team may belong to different organization units, divisions, or even different organizations.

It is mandatory to have only one team selected, and this has in impact on what Work Queues are visible in Case Manager Portal for the user.

Click the plus sign to add the additional teams to which this user belongs.

The specified value is used by the display shown when you click Reporting structure. The field has no additional uses.

In the displayed hierarchy, the names of operators who are not available are marked with a distinctive light blue background.

Routing activities and security tests can access skill information recorded here to determine which assignments this operator can perform. Order in this array is not significant.

This array is visible only if the Use all work queue assignments in user's team check box is not selected.

Your changes to this array may take effect only after the LookupList cache is rebuilt and the later operator logs in.

This list does not restrict the ability of users to open and complete assignments placed in other work queues. Normally, users can fetch assignments directly from any work queue defined for their own organization unit, bypassing the Get Next Work facility.

For general information on this facility, see Maximizing user productivity with GetNextWork.

Clear to prevent routing shapes in flow executions from adding assignments to this user's worklist.

This check box affects only routing activities. This check box does not affect the ability of this user to log in, enter work items, or complete assignments already on the worklist. It does not prevent another operator or manager from transferring assignments to the worklist.

If selected and at runtime a router activity (with parameter CheckAvailability set to true) attempts to send an assignment to the worklist of this operator ID, the substitute operator if any is used instead. If no substitute is found, the router activity adds the assignment to the worklist of the manager of this operator's team.

• When selected, system retrieves an assignment from the user's worklist only when all of the work queues listed in the Work queues array are empty.
• If not selected, Next Assignment, when clicked, retrieves the top assignment on the user worklist, and accesses work queues only if this user's worklist is empty.

Work queues can be set up so that only users who possess one of a list of access roles can remove assignments from them. Processing for the Next Assignment facility skips over any work queue that this user cannot fetch assignments from.

This processing ignores Error: assignments ( problem assignments ); they are never selected as most urgent.

Your application can alter or override the standard activities that support this button, providing a sophisticated means of prioritizing which assignments users work on. See Maximizing user productivity with GetNextWork.

This field is visible only when the Merge work queues check box is selected.

When enabled, selection and sorting occurs directly through efficient SQL operations on tables in the PegaRULES database. This is typically faster than activity-based searching and sorting

When enabled, selection and sorting occurs directly through efficient SQL operations on tables in the PegaRULES database. This is typically faster than activity-based searching and sorting.

Select a valid calendar carefully. To simplify and reduce maintenance over multiple years, this value is not validated when you save an Operator ID form.

As a best practice, if all or nearly all operators in an organization are in a single time zone and follow a common business day calendar, leave this field blank for those operators who share the organizational calendar and time zone. Complete the Calendar and Time Zone fields only for the operators who are exceptions.

Few standard rules depend on the value in this field; it is provided for application use. The calendar does not affect the ability of the operator to sign on, enter work, or perform assignments.

Your application can use this field to access a calendar data instance for the operator when calling date functions. For example, if the value of this field is HONGKONG and the current date is March 31, 2006, the system first searches for a calendar with key HONGKONG.20060331. If no calendar data instance exactly matches this key, the immediately preceding calendar instance if any that matches HONGKONG (such as HONGKONG.20060101) is used.

During log-in, if this field is not blank, both the calendar and the time zone are set on the requestor page as the calendar and default time zone (property pyRequestorTimeZone ). If blank, the system uses the calendar from the Organization data instance and does not set a time zone; the time zone is then typically defaulted to the time zone of the server node.

Click the + icon to add a row. Click the calendar icon to select a date from the pop-up calendar.

Most operators cannot update this information directly. A team manager can update this information, for operators in the group. (The standard privilege named Data-Admin-Operator-ID.UpdateWorkgroupAvailability conveys this capability.)

The system purges past time intervals from this list each time the operator logs in.

• Operator — To attempt to route new assignments to another operator when this operator is not available to accept new assignments.
• Work queue — To place new assignments for this operator into a work queue when this operator is not available to accept new assignments.

To find this decision tree, the system uses Data-Admin-Operator-ID as the initial value of the Applies To class.

The system uses the substitute operator or work queue if the First, use this Decision Tree field is blank, or the decision tree does not result in a valid operator ID or work queue value.