IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building human tasks
Ad hoc collaboration
When you create or modify a task in the user interface of the runtime environment, you can dynamically define a task either as a subtask or a follow-on task.
Ad hoc tasks and transferred work items are created "on-the-fly" in the runtime environment, usually because of new circumstances that did not exist when the task was initially developed. Such tasks can be used when the application is stand-alone, and when the task is either to-do or collaboration.
You can use IBM Integration Designer to allow for two types of ad hoc tasks (the subtask and the follow-on task), as well as the transferred work item (see below). To create a pure ad hoc task, you would use the Human Task API to define a dynamic Human Task template, deploy this to an application server, and then start an instance of it. For an example of such an ad hoc task, go to 
http://publib.boulder.ibm.com/bpcsamp/index.html, and click Human Task features > Ad hoc Human Task.
You will need a connection to the internet to view this example.
- Subtasks
In the runtime environment, if a person who claims a task finds that they are not able to complete it by themselves, they can delegate portions of that original task to other people in the form of subtasks. - 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.
Related concepts:
Versioning business state machines
Before you begin: Client types and prerequisites
Related tasks:
Supporting other languages
Related reference:
Details tab: business state machine editor