- Introduction and getting started
- Maestro landing page
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
A task is the most fundamental unit of work in BPMN. It represents an activity that must be performed, either by a person, a system, or a rule engine. Tasks form the core of every process diagram and should be modeled clearly to reflect business intent.
This section explains how to use different BPMN task types when modeling in Maestro, along with notes on visual usage, supported runtime behavior, and common design patterns.
Tasks can vary based on who performs them or how they behave. Maestro supports several BPMN task types for both modeling and execution. Other types may be used for visual completeness but are not interpreted by the engine.
| Task type | Icon | Description | Use in modeling | Execution support in Maestro |
|---|---|---|---|---|
| User task | Work performed manually by a person via Task Inbox | |||
| Service task | Work executed by an automation, API, or system | |||
| Script task | System logic evaluated inline (e.g., an expression) | |||
| Business Rule task | Evaluates decision logic via DMN or rule engine | |||
| Manual task | Informal activity done manually, not tracked | |||
| Send task | Represents a message being sent | |||
| Receive task | Waits for a message to arrive |
- Use user tasks to represent manual steps requiring human input.
- Use service tasks to invoke automations or APIs.
- Use script tasks for decision expressions or flow logic.
- Use business rule tasks for branching based on rules (e.g., DMN).
- Use manual, send, or receive tasks only when documenting interactions not handled in Maestro.
Certain task types can be further annotated using markers, such as:
- Multi-instance (parallel or sequential): To repeat the task for items in a collection.
- Loop: For modeling intended repetition.
- Compensation: To indicate rollback logic.
For full details, refer to Markers.
Use a call activity instead of a task when:
- The activity refers to a separately modeled sub-process.
- The logic is reused in multiple workflows.
- Input/output mapping is needed across diagrams.
- Keep task names concise and business-oriented.
- Assign one clear purpose per task.
- Avoid modeling ambiguous or placeholder tasks (Process Something).
- Group related tasks in sub-processes if the diagram grows large.
For more details about the BPMN elements supported in Maestro, see BPMN support.
