12.2.2.5.2 Task

Assigning BPMN Properties to Tasks

Modelers have the capability to assign BPMN properties directly to shapes while working in the Diagram Editor.

Assigning BPMN Properties to a Task

*Ensure you are given Write Permission and the displayed content is set to Latest.

1. Navigate to the Diagram Editor.
2. Choose an existing task or create one.
3. Right-click on the task.
4. A drop-down menu will be generated.
5. Choose the Edit BPMN Properties option.

6. A pop-up will be generated allowing you to choose the BPMN Properties for the task.

Ad-hoc

Click on the box to enable the Ad-Hoc property for the task.

*Ad hoc tasks represent flexible, user-driven activities within a process, allowing tasks to be performed as needed, without a predefined sequence. These tasks offer dynamic execution, enabling users to initiate and complete them based on specific process instances and requirements.

Compensation

Click on the box to enable the Compensation property for the task.

*A compensation task is a type of task used to handle the compensation of activities that have already been completed within a process. These tasks are designed to undo or reverse the effects of previously executed tasks in case of errors, exceptions, or other abnormal situations. Compensation tasks are typically associated with specific activities in the process and are triggered when those activities encounter errors or need to be rolled back.

Loop Characteristics

There are three loop options:

1. Loop

*A loop is a construct used to repeat a sequence of activities multiple times based on a condition or criteria specified in the process. When a loop is encountered during process execution, the activities within the loop are repeated until the loop condition is no longer satisfied.

2. Parallel Loop

*In a parallel loop, multiple instances of the looped activities are executed concurrently or in parallel. This means that each iteration of the loop runs independently of the others, allowing for simultaneous execution of multiple instances of the loop.

3. Sequential Loop

*A sequential loop executes multiple instances of the looped activities sequentially or one after the other. Each iteration of the loop is executed in sequence, with the next iteration starting only after the previous one has completed.

Task Type

There are eight task type options:

1. Abstract

*An abstract task acts as a placeholder within a process model, representing activities that are not fully defined within the model itself.

2. Send

*A send task represents an activity within a process that initiates the sending of a message or communication to an external recipient or system. Send tasks are typically used to model interactions with external systems, services, or participants.

3. Receive

*A receive task represents a point in a process where the flow is paused until a specific message or signal is received from an external participant or system.

4. User

*A user task represents a task that requires human interaction or manual intervention to be completed. It typically involves a user performing a specific activity within a business process, such as reviewing a document, approving a request, or entering data into a system.

5. Manual

*A manual task represents an activity within a process that requires human intervention or manual effort to complete. These tasks typically involve actions performed by a human operator, such as data entry, document review, or decision-making.

6. Business Rule

*A business rule task represents a specific type of task that executes a business rule or decision within a process. These tasks encapsulate the execution of business rules, such as validation criteria or decision logic, enabling the automation of rule-based processes.

7. Service

*A service task represents work performed by a software service, application, or external system within a process. It encapsulates activities that are automated and performed outside the process model, typically invoking a service or application to execute specific functions or tasks.

8. Script

*A script task is a type of task that represents an activity within a process that is implemented using a script or code snippet. These tasks are used to execute custom logic or operations within the process, allowing for more flexibility and automation. Script tasks typically involve the execution of scripts written in languages such as JavaScript, Groovy, or Python, enabling process designers to implement complex behaviors and interactions within the process model.