Editing BPMN (section)

=====Task=====
* is atomic
* starts immediately after the predecessor activity, this is at least from the modeling view also true for user tasks*
* can have markers:
** Loop
** Multi-Instance
** Compensation
** Loop and Compensation
** Multi-Instance and Compensation
* task type can be represented by an icon. [[#Task_Types|Task types]] are:
** Abstract or Undefined Task
** [[#Send_Task|Send]]
** [[#Receive_Task|Receive]]
** [[#User_Task|User]]
** [[#Manual_Task|Manual]]
** [[#Business_Rule_Task|Business Rule]]
** [[#Service_Task|Service]]
** [[#Script_Task|Script]]

======Send Task======
* A Send Task is a simple Task that is designed to send a Message to an external Participant. Once the Message has been sent, the Task is completed.
* The difference to a throwing [[#Message_Intermediate_Event|Message Intermediate Event]] is:
** it can have a Multi-Instance marker
** it can have boundary events

======Receive Task======
* A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant. Once the Message has been received, the Task is completed.
* Can start a process, but must not have any incoming sequence flow in this case. In this case the envelope is inside a circle.

======User Task======
* A User Task is executed by and managed by a business process runtime. Attributes concerning the human involvement, like people assignments and UI rendering can be specified in great detail.
* A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.

======Manual Task======
* A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.
* A Manual Task is neither executed by nor managed by a business process runtime.

======Business Rule Task======
* A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.

======Service Task======
* A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application.
* should be used for synchronous calls

======Script Task======
* A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.
* has exactly one input set and at most one output set