Information Technology Reference
In-Depth Information
A task in the
Reserved
state is only available for one user, so it is ready to be started by
the claimer. The claimer, once ready to begin working on the task, can start it by moving it
to the
InProgress
state. The task will usually remain in that state until the user in charge
of that task completes it, moving it to the
Completed
state. Alternatively, we can suspend
or stop the task, which means that we need to resume it or start it again.
In situations where a task cannot be successfully completed, we can use four other close
strategies for the tasks. If it cannot be successfully completed, the Fault task operation
moves the task to the
Failed
state. This is usually done when the user in charge of the task
doesn't have all the information or the means that is required to finish the task.
Error
,
Exit
, and
Obsolete
are used when there is an error inside the task or the task is no longer
needed.
Determining who is the right person to complete a specific task is the responsibility of the
Human task service, and it will do it based on the input information received from the task
creation process. Now that we understand the states that a task can be in, we can get into
the API side to understand how these operations translate to code invocations and how
this extra information is shared between processes and tasks. The following section intro-
duces the Human task component provided in jBPM6 by showing us an example of how
to create Human tasks.
