- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
BPMN 2.0 elements supported on the Maestro canvas, with execution availability status for Start, Intermediate, and End event types.
The Maestro canvas conforms to the BPMN 2.0 standard, and supports the following Start, Intermediate, and End elements for execution. All elements are supported for modeling.
Legend:
✅ = Available for execution
❌ = Not available for execution
Events
Start execution elements
| Type | Normal | Event sub-process | Event sub-process non-interrupting |
|---|---|---|---|
| None | ✅ | ❌ | ❌ |
| Message* | ✅ | ❌ | ❌ |
| Timer | ✅ | ❌ | ❌ |
| Error | ❌ | ❌ | ❌ |
| Signal | ❌ | ❌ | ❌ |
| Conditional | ❌ | ❌ | ❌ |
| Escalation | ❌ | ❌ | ❌ |
| Compensation | ❌ | ❌ | ❌ |
| Cancel | ❌ | ❌ | ❌ |
| Terminate | ❌ | ❌ | ❌ |
| Link | ❌ | ❌ | ❌ |
| Multiple | ❌ | ❌ | ❌ |
| Multiple parallel | ❌ | ❌ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
* These elements are supported for execution via Integration Service connectors.
Intermediate execution elements
| Type | Catch | Boundary | Boundary non-interrupting | Throw |
|---|---|---|---|---|
| None | ❌ | ❌ | ❌ | ✅ |
| Message* | ✅ | ✅ | ✅ | ✅ |
| Timer | ✅ | ✅ | ✅ | ❌ |
| Error | ❌ | ✅ | ❌ | ❌ |
| Signal | ❌ | ❌ | ❌ | ❌ |
| Conditional | ❌ | ❌ | ❌ | ❌ |
| Escalation | ❌ | ❌ | ❌ | ❌ |
| Compensation | ❌ | ❌ | ❌ | ❌ |
| Cancel | ❌ | ❌ | ❌ | ❌ |
| Terminate | ❌ | ❌ | ❌ | ❌ |
| Link | ❌ | ❌ | ❌ | ❌ |
| Multiple | ❌ | ❌ | ❌ | ❌ |
| Multiple parallel | ❌ | ❌ | ❌ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
- These elements are supported for execution via Integration Service connectors.
End execution elements
| Type | End |
|---|---|
| None | ✅ |
| Message* | ✅ |
| Timer | ❌ |
| Error | ✅ |
| Signal | ❌ |
| Conditional | ❌ |
| Escalation | ❌ |
| Compensation | ❌ |
| Cancel | ❌ |
| Terminate | ✅ |
| Link | ❌ |
| Multiple | ❌ |
| Multiple parallel | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
* These elements are supported for execution via Integration Service.
Non-events
Tasks
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Undefined Task | ✅ | ✅ |
| User Task* | ✅ | ✅ |
| Service Task | ✅ | ✅ |
| Receive Task** | ✅ | ✅ |
| Send Task** | ✅ | ✅ |
| Business Rule Task | ✅ | ✅ |
| Script Task | ✅ | ✅ |
| Manual Task | ✅ | ✅ |
| Receive Task (instantiated) | ✅ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
* With UiPath Apps.
** These elements are supported for execution via Integration Service connectors.
Gateways
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Exclusive Gateway | ✅ | ✅ |
| Parallel Gateway | ✅ | ✅ |
| Inclusive Gateway | ✅ | ✅ |
| Event Gateway | ✅ | ✅ |
| Complex Gateway | ✅ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
Markers
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Multi-instance parallel | ✅ | ✅ |
| Multi-instance sequential | ✅ | ✅ |
| Loop | ✅ | ❌ |
| Compensation | ❌ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
Data
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Data Object | ✅ | ❌ |
| Data Store | ✅ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
Artifacts
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Text Annotation | ✅ | ❌ |
| Group | ✅ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
Participants
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Pool | ✅ | ❌ |
| Lane | ✅ | ❌ |
All elements are supported for modeling. The ❌ mark only refers to execution support.
Sub-processes
| BPMN construct | Supported in Modeler | Supported in Execution |
|---|---|---|
| Sub-process | ✅ | ✅ |
| Call activity | ✅ | ✅ |
| Event sub-process | ✅ | ✅ |
| Transaction | ❌ | ❌ |
UiPath Maestro™ does not support collapsed pools (also known as black box pools), which are pools that do not display their internal process flow.