Normally, PRPC only routes assignments to the worklists of users who are available. Information in the Operator ID data instance determines whether a user is available. A user is available if both conditions are true:
If routing for an assignment attempts to send the assignment to the worklist of an operator who is not available, PRPC can use a rule referenced in the Operator ID instance to identify a substitute operator.
If no substitute is available, the routing activity sends the assignment to the worklist of the operator's manager.
Availability only affects the routing of assignments. The worklist of an unavailable user may or may not be empty; it can contain assignments sent before the operator became unavailable, or assignments transferred by a manager or another user.
User availability is unrelated to use of PRPC applications. During a period when an user is marked as unavailable, that user can log in, work on older assignments, and enter new work items (which can create assignments routed to others or to workbaskets).
Developers and work managers have the privilege needed to update the availability and scheduled absences information in Operator ID data instances, such as for vacations. The standard privilege named Data-Admin-Operator-ID.UpdateWorkgroupAvailability conveys this capability.
assignment, profile, router shape, work manager, worklist | |
About Operator ID data instances |