Page 290 -

286 M. Adams
and a user-initiated start interaction specified at design time, and the participant
is a member of the specified distribution set and the specified allocation strategy
employed has resulted in the participant being chosen to be allocated the work item;
the task from which the work item was created had a user-initiated start interaction
specified at design time, and the participant has chosen the Accept Offer action for
the work item on the offered queue; the task from which the work item was created
had a user-initiated offer interaction specified at design time or had an empty or
invalid resourcing specification, and an administrator has manually allocated the
work item to the participant; the work item has been delegated by another partici-
pant (see below); or an administrator has manually reallocated the work item to the
participant, the work item having previously been allocated to or started by another
participant.
A participant may take the following actions on a work item in an allocated
queue:
Start: The work item is started (i.e., begins executing), and moved to the
participant’s started queue.
Deallocate: This action provides an authorized participant with a means of reject-
ing the allocation of a work item. The work item is removed from the participant’s
allocated queue, the participant is removed from the original distribution set (if
any), and the work item is redistributed as per the resourcing specification. If
there is no distribution set or there is an empty or invalid resourcing specification
for the task from which the work item was created, the work item is placed on
the administrator’s unoffered queue for manual distribution. A participant must
have the task privilege “Can Deallocate” to enable deallocation.
Delegate: This action allows a participant to delegate responsibility for a work-
item to another participant. The receiving participant must be subordinate to
the delegating participant in the organizational model, that is, the receiving par-
ticipant must hold a position that reports to a position held by the delegating
participant, either directly or through a hierarchy of positions. The work item is
moved from the allocated queue of the delegator to the allocated queue of the
receiver. A participant must have the task privilege “Can Delegate” and have
subordinate staff to successfully deallocate a work item.
Skip: This action skips the execution of the work item, that is, the work item is
immediately started and then completed, allowing the process to continue accord-
ing to its subsequent control-flow.A participant must have the task privilege “Can
Skip” to enable the skipping of a work item.
Pile: When a work item is piled, the work item is immediately started and placed
in the participant’s started queue. Furthermore, each and every future instance
of the work item across all cases (of the same specification) is automatically
allocated to the participant and started, completely ignoring any resourcing spec-
ification for the task from which the work item is created. To put it another way,
by piling a work item, a participant is entering into a contract with the Resource
Service, asking that this work item, and all future occurrences of such work items
created from the same task description as the original work item was created
from, be immediately allocated and started to him/her. Piling of such work items