Page 62 -

2 The Language: Rationale and Fundamentals 49
once the emergency-shutdown work item is allocated to user jsmith, change its
state to started.
Chained Execution corresponds the ability to automatically start the next work
item in a case once the previous one has completed. Typically, the use of this pat-
tern falls under the auspices of an individual resource for work items associated
with a specific case, for example, for the current case, user jsmith indicates that
as soon as they have completed a work item, the following work item should be
automatically allocated to them in a started state.
Piled Execution corresponds to the ability to initiate the next instance of a work
item corresponding to a given task (perhaps in a different case) once the previous
one has completed, such that all work items are allocated to the same resource.
Typically, the use of this pattern falls under the auspices of an individual resource
for work items associated with a specific task. Only one resource can be in Piled
Execution mode for a given task at any time, for example, user jsmith indicates
they wish to undertake any instances of the finalize-audit work item regardless
of the case in which they arise. In the interest of expediting the completion of
these work items, they are to be automatically allocated to jsmith’s worklist in a
started state.
The various patterns discussed thus far focus on various qualities associated with
the distribution of work items. In contrast, the next group – visibility patterns – deal
with the external observability of work items in a process.

Visibility Patterns

Visibility patterns delineate the ability to configure the extent of disclosure about
the state of progress on particular work items. There are two such patterns.
Configurable Unallocated Work Item Visibility corresponds to the ability to
configure the visibility of unallocated work items by process participants, for
example, restrict the reporting of work items not yet allocated or started to users
to whom they might be offered
Configurable Allocated Work Item Visibility corresponds to the ability to config-
ure the visibility of allocated or executing work items by process participants, for
example, allow any users to see the state of allocated or started instances of the
adjudicate-case work item.

The final group of patterns – multiple resource patterns – deal with variations in the
cardinality between work items and resources.

Multiple Resource Patterns

Multiple resource patterns identify work situations where the correspondence
between work items and resources is not one-to-one. There are two of these patterns.