Information Technology Reference
In-Depth Information
In the preceding figure, we can see that external components can interact with any of the
components related to jBPM6, regardless of whether we're talking about processes, rules,
or human interactions. The sort of information exposed through the listeners in the Human
task engine is, however, closely related to the task's internal life cycle. We'll now provide
an overview of it.
Human tasks' life cycle
The WS-HT specification defines a detailed and complete set of states that every task can
be in as well as operations allowed to change a task from one status to the next. These
states are designed to cover almost every possible scenario related to Human tasks.
These statuses also cover what we call Group tasks, which are assigned to a group instead
of a particular person. Business processes can create these tasks, and anyone who belongs
to the defined groups can complete them. When tasks are created, every person in the
group who wishes to complete them will have to claim each task in order to work on it.
Claimed tasks are assigned to the claimer only, and no one else can
claim
that task. If the
claimer of the task cannot work on it, he or she has the option to
release
it.
The following graph represents the possible states and transitions of a task according to
the specification:
