Tasks are closely integrated with webMethods business process models. A task can be added to a business process as a user task activity, also referred to as a user task. Each user task can represent a discrete human activity within the process, such as installing a piece of equipment, but in more advanced processes, you might want to create a series of user tasks, where each user task step represents one activity in a larger, overall procedure.

When you connect a series of tasks together in this way, you are creating a task workflow, also referred to as a form flow.

A task workflow enables you to break up a complicated procedure into a series of simpler user task steps. Task orchestration is done by the process model and not inside a single task that could become overly complex and difficult to deploy, maintain, use, and understand.

In a task workflow, you can use the more sophisticated logic of the process model to determine which task to start and the next task interface to display to the user. The process model can call additional services to implement any necessary business logic between tasks steps. As the task workflow progresses, the individual tasks open automatically; the user does not have to manually open each individual task.

In a typical task flow scenario, a previous step in a business process completes and then transitions to and starts (or queues) a user task as the next step in the process.

For example: