Task

Is an atomic Activity within a Process flow. It is used when the work in the Process cannot be broken down to a finer level of detail.

User Task

Is a typical workflow Task where a person performs the Task with the assistance of a software application.

Service Task

Is a Task that uses some sort of service that could be a Web service or an automated application.

Receive Task

Is a Task designed to wait for a message to arrive from an external participant (relative to the Process).

Send Task

Is a Task designed to send a message to an external participant (relative to the Process).

Script Task

Is a Task that is executed by a Business Process Engine. The Modeler defines a script in a language that the engine can interpret.

Manual Task

Is a Task that is expected to be performed without the aid of any business process execution or any application.

Business Rule Task

Offers a mechanism for the Process to provide input to a Business Rule Engine and get the output of calculations that the engine might provide.

Multi-Instance Loop

Tasks may be repeated sequentially,  behaving like a loop. The Multi-instance Loop iterates a predetermined number of times.  The iterations occur sequentially or in parallel (simultaneously).

Standard Loop

Tasks may be repeated sequentially, behaving like a loop. This feature  defines a looping behavior based on a Boolean condition. The Activity will loop as long as the Boolean condition is true.

Sub-process

Is an Activity which internal details have been modeled using activities, gateways, Events, and sequence flows. The elements has a thin border.

Reusable Sub-process

Identifies a point in the Process where a predefined Process is used. A reusable Sub-process is called a Call Activity in BPMN.  The element has a thick border.

Event Sub-process

A Sub-process is defined as an Event Sub-process when it is triggered by an Event. An Event Sub-Process is not part of the normal flow of its parent Process - there are no incoming or outgoing Sequence Flows.

Transaction

Is a Sub-process whose behavior is controlled through a transaction protocol. It includes the three basic outcomes of a transaction: Successful Completion, Failed Completion and Cancel Intermediate Event.

Ad-Hoc Sub-process

Is  a group of activities that has no REQUIRED sequence relationships. A set of activities can be defined, but the sequence and number of performances for the activities is determined by the resources of the activities.

Standard loop

Sub-processes may be repeated sequentially, behaving like a loop.

This feature defines a looping behavior based on a Boolean condition. The activity will loop as long as the Boolean condition is true.

Multi-Instance loop

Sub-processes may be repeated sequentially, behaving like a loop.

The Multi-instance Loop iterates a predetermined number of times.  The iterations occur sequentially or in parallel (simultaneously).