IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building human tasks > Ad hoc collaboration
Follow-on tasks
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.
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.
Example
To see an example of a follow-on
task that you can build and run yourself, go to 
http://publib.boulder.ibm.com/bpcsamp/index.html, and click Human Task features > Follow-on task.
You will need a connection to the internet to view this example.