Operator ID form
Completing the Work tab

Field

Description

Click Update to select an organization, division and unit from the pop-up window.

Select the name of a work group (a Data-Admin-WorkGroup instance). Work groups are the basis of many standard management reports.

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

Optional. Select the Operator ID of another user to whom this operator reports.

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

Click to display the reporting structure for this operator, based on the values specified in the Reports To field for this operator and for other operators. A new window opens displaying the reporting structure. The system assembles and displays a hierarchy (tree) view.

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

Optional. Identify a skill name — the name of a skill rule (Rule-Admin-Skill rule type) associated with this user.

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.

Optional. Select a user proficiency rating for this skill between 1 and 10, where 10 indicates highest proficiency. (Some skill rules may allow only a narrower range of ratings, such as 1 to 3.)

Optional. Enter a list of workbaskets that may contain assignments for this user. When this user clicks the Get Next Work menu item to obtain an assignment, the system searches the workbaskets listed here in order (unless the Merge workbaskets box is selected.) The Get from workbaskets first check box controls whether the system searches the workbaskets or the worklist first, and other aspects of the search algorithm.

This array is visible only if the Use all workbasket assignments in user's work group 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 workbaskets. Normally, users can fetch assignments directly from any workbasket defined for their own organizational unit, bypassing the Get Next Work facility.

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

Optional. For each workbasket, enter a minimum value for the assignment urgency value. During  Get Next Work  processing, assignments in this workbasket with an urgency less than this value are ignored.

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

Select to allow applications to route additional assignments to the worklist of the user who is identified by this Operator ID data instance.

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 routing 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 routing activity adds the assignment to the worklist of the manager of this operator's work group.

Select to cause the Get Next Work menu item to consolidate assignments from all the workbaskets in the Workbaskets array below, then sorted by assignment urgency, returning the most urgent in any workbasket.

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 to have Get Next Work processing assemble and sort assignments in any workbasket for which the Work Group field (on the Workbasket tab of the Workbasket form) is the same as the Work Group field of this operator (as set on the Operator tab).

This field is visible only when the Merge workbaskets 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

Select to cause the Get Next Work menu item retrieve assignments first from workbaskets listed below.

• When selected, system retrieves an assignment from the user's worklist only when all of the workbaskets listed in the Workbaskets array are empty.
• If not selected, the  Get Most Urgent   button when clicked retrieves the top assignment on the user worklist, and accesses workbaskets only if this user's worklist is empty.

Workbaskets 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  Get Most Urgent   facility skips over any workbasket 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.

Field

Description

Optional. Select a time zone to be used for presenting dates and times to this user in:

• Work object history
• List view reports on work items and assignments
• Summary view reports on work items and assignments

For example, select America/New_York for the US Eastern time zone; the display adjusts correctly for daylight savings time. Select Europe/London for London time.

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.

These values are grouped by zone, not alphabetically, in the drop-down list, starting with the zone that is 12 hours away from Greenwich, England. Time zone codes follow the Olson TZ database, used in the ICU4J 3.4.4 library and most UNIX systems. Details on the Olson TZ database are available from http://en.wikipedia.org/wiki/Tz_database.

Do not type a three-letter code in this field, as such codes are ambiguous in certain cases and may produce incorrect presentation of daylight savings time in other cases. For details, see Pega Developer article Issue: Avoid three-letter time zone codes because they do not support Daylight Savings Time.

Settings in this field only affect the presentation of DateTime values. Within the database, all DateTime values are recorded in universal time, informally known as GMT. As a result, a work item resolved in one country on Tuesday may be presented as resolved on Monday when the history is reviewed in another country.

As a best practice, if your organization has all its staff and servers in a single time zone, leave the Calendar and Time Zone fields blank. If most staff and all servers are in a common time zone, leave the Calendar field blank but complete a Time Zone value for the exceptional operators. If the organization has operators and servers across many time zones, create a Calendar for each time zone and specify both the Calendar and Time Zone fields in every Operator ID instance.

In PRPC Version 4, three-letter Java time zone codes such as EST for Eastern Standard Time were accepted for this field. Some — but not all — of the three-letter Java codes are also Olson time zone codes.

Select a valid calendar carefully. To simplify and reduce maintenance over multiple years, PRPC does not validate the value in this field 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.

Optional. Identify one or more future date intervals during which this operator is not available. In testing the current date time against the date ranges here, the system uses the calendar (and the time zone of the calendar) associated with this operator.

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 work group manager can update this information, for operators in the group, from the Process Work workspace. (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.

Select:

• Operator — To cause the system to attempt to route new assignments to another operator when this operator is not available to accept new assignments.
• Workbasket — To place new assignments for this operator into a workbasket when this operator is not available to accept new assignments.

Optional. Identify the name (second key part) of a decision tree that the system can use to identify a substitute who can receive assignments sent to this operator. Select a decision tree that returns an Operator ID or one that returns a workbasket name, matching your selection in the Assignee Type field.

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

Optional. Identify the Operator ID or workbasket name of a substitute for new assignments routed to the user identified by this Operator ID instance when that user is unavailable.

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