Page 58 -

2 The Language: Rationale and Fundamentals 45
the same user within a given process instance, for example, the sign-cheque task
cannot be undertaken by the same user who completed the lodge-purchase-order
task.
Case Handling corresponds to the ability to allocate all work items in a case to
the same resource at the time of commencement, for example, all work items in
an instance of the insurance claim process are allocated to user jsmith.
Retain Familiar corresponds to a constraint that exists between two tasks, requir-
ing that where possible they be executed by the same user within a given process
instance, for example, the order-materials task should be undertaken by the same
user who completed the calculate-materials task.
Capability-based Distribution corresponds to the situation where a work item
is offered or allocated to one or more resources based on capabilities that they
possess, for example, allocate the audit account task to a user having a CPA
qualification.
Organization-based Distribution corresponds to the situation where a work item
is offered or allocated to one or more resources based on their position or other
responsibilities within the organization, for example, allocate the authorize order
task to a user at the level of manager or above.
History-based Distribution corresponds to the situation where a work item is
offered or allocated to one or more resources based on their preceding execution
history, for example, allocate the audit major customer task to the user who has
completed most audits in the past three months.
Automatic Execution corresponds to the situation where a work item can be exe-
cuted without needing to be distributed to a resource, for example, the send-order
work item can execute automatically without requiring a user to complete it.
While this set of patterns focus on establishing the identity of the resources to which
work items should be distributed, the next group – push patterns – deal with the
manner in which the system having identified the resources can distribute work
items to them.

Push Patterns

Push patterns apply in situations where work items are forwarded to resources by
the system that is automating a business process. These patterns correspond to the
offer and allocate arcs initiated by the system (i.e., tagged (S)) in Fig. 2.12. The
various push patterns are as follows.
Distribution by Offer – Single Resource corresponds to the situation where a
work item is offered to a specific resource on a nonbinding basis, for example,
the review-feedback work item is offered to user jsmith to complete, although
they are not obliged to do so.
Distribution by Offer – Multiple Resources corresponds to the situation
where a work item is offered to several resources on a nonbinding basis with the
expectation that one of them might commit to undertaking it, for example, the