In the runtime environment, if a person who claims a task
finds that they are not able to complete it, they can assign the remaining
work to somebody else in the form of a follow-on task.
About this task
Follow-on tasks can be derived from inline or stand-alone
to-do tasks as well as collaboration tasks, and can be realized as
a collaboration or stand-alone originating task. They can also support
subtasks, as well as further follow-on tasks. The input, output, and
fault message definitions of the completed and the follow-on task
must be of the same type. The initial task that spawns the follow-on
task is called the predecessor task, and in cases where there
is a chain of follow-on tasks, the first task in the chain is known
as the head task.When you are first creating the human task
template, you can decide if the business case justifies the need for
the creation of follow-on tasks, and configure your template accordingly.
To control the creation of follow-on tasks, proceed as follows:
Procedure
- Open your task in the human task editor.
- In the Details tab of the properties area, configure
the Enable follow-on task creation check box
as follows:
| Option |
Description |
|---|
| Selected |
If this check box is selected, then this human task template
will allow for the creation of follow-on tasks in the runtime environment. |
| Cleared |
If this check box is cleared, then users will not be able
to delegate portions of this task in the from of follow-on tasks. |
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15