maestro
latest
false
Maestro user guide
- 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
- Accessing the Maestro API
- Maestro BPMN to Maestro Flow concept mapping
- Maestro and ReFramework FAQ
- Downloads
Business Process Model and Notation (BPMN) 2.0 concepts and their Flow equivalents, for process architects familiar with BPMN.
This reference is for developers and architects who are familiar with Business Process Model and Notation (BPMN) 2.0 and want to understand how Maestro BPMN concepts map to Flow equivalents.
For a higher-level comparison of when to use each tool, see Choosing a Maestro modeler.
Concept mapping table
| BPMN concept | Maestro BPMN | Flow equivalent |
|---|---|---|
| Start event | Start event node | Manual Trigger or Scheduled Trigger node |
| End event | End event node | Terminate node (or natural end of canvas) |
| Task | Service task, user task | HTTP Request, Script, Data Transform, or Human node |
| Exclusive gateway | XOR gateway | Decision node |
| Parallel gateway | AND gateway | Parallel branches + Merge node |
| Inclusive gateway | OR gateway | Multiple Decision nodes or Switch node |
| Subprocess | Collapsed subprocess | Subflow node |
| Boundary error event | Error boundary event | Error handle on a node |
| Sequence flow | Sequence flow | Connection between nodes |
| Data object | Data object | Variable |
| Pool / lane | Pool / lane | Not applicable — Flow does not use swim lanes |
| Timer event | Timer boundary event | Scheduled Trigger node |
| Message event | Message catch event | Integration trigger node |
Key differences
- No swim lanes — Flow does not model organizational roles or participants as swim lanes. Human assignment is handled at the node level via the Human node.
- No BPMN XML — Flow uses the
.flowJSON format, not BPMN XML. Workflows cannot be directly imported from a BPMN modeler. - Error handling is inline — Flow handles errors at the node level via each node's error handle, rather than using boundary events attached to tasks.
- No compensation — BPMN compensation flows have no direct equivalent in Flow. Compensation logic is represented explicitly with Decision and error handler nodes.