- Introduction
- Getting started
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
Business Process Model and Notation (BPMN) is an open standard maintained by the Object Management Group (OMG) and widely adopted for modeling complex business processes. Its visual format helps bridge the gap between technical and non-technical stakeholders, making it easier to design, review, and collaborate on process logic.
In Maestro, BPMN is the language you use to turn real‑world processes into automation‑ready models: you sketch the logic, define the hand‑offs, and specify the triggers and outcomes—then refine that model until it’s precise enough to run.
BPMN includes a rich set of symbols (events, tasks, gateways, flows, and artifacts). Maestro focuses on the most practical subset for automation so that your diagrams remain clear, unambiguous, and executable. Think of a BPMN diagram in Maestro as a contract:
- It’s human‑readable (any stakeholder can review the logic).
- It’s machine‑actionable (Maestro can validate and orchestrate it).
- It’s maintainable (changes to the diagram modify the behavior, without any hidden logic).
A typical automation starts with a trigger (an incoming message, a schedule, or a button click), proceeds through work steps (human or system), branches with decisions, and ends with a result (completed, canceled, or failed with an error). BPMN gives you the building blocks for each of these stages, and Maestro provides the guardrails—naming conventions, validation, and execution semantics—so your models behave exactly as drawn.
In Maestro, BPMN provides the foundation for modeling automation workflows that are both human-readable and execution-ready. This chapter introduces the core BPMN elements used in Maestro—Events, Tasks, Gateways, and more—so you can build clear, consistent process models that align with both business needs and automation goals.
This primer orients you to the BPMN elements you’ll actually use in Maestro and how to choose among them:
- Events in BPMN
modeling
Events mark something that happens: a process start (e.g., message or timer), something occurring mid‑flow (e.g., wait for a reply, catch a signal, handle a timeout), or a process end (success, escalation, error). You’ll learn how to pick the right event type to model triggers, waits, timeouts, and error handling cleanly.
- Tasks in BPMN
modeling
Tasks represent work to be performed. You’ll see when to use user‑driven steps (approvals, data entry) versus system‑driven steps (API calls, scripts), and how to encapsulate reusable logic with subprocesses and call activities.
- Gateways (decision and sync
points)
Gateways control the path of execution: choose one path (exclusive), take many paths (parallel), or take the matching set (inclusive). You’ll learn patterns for routing, merging, and avoiding deadlocks or orphaned tokens.
- Markers (behavior
qualifiers)
Markers modify how a task or subprocess behaves: looping, multi‑instance (run once per item), ad‑hoc, or compensation. You’ll learn when markers make intent explicit and when a simpler pattern reads better.
- Sequence vs. message
flows
Sequence flows show order of work inside a participant; message flows show communication between participants (e.g., your process and an external system or partner). You’ll learn how to keep responsibilities clear with pools and lanes.
- Data and artifacts
Data objects, data stores, annotations, and groups help you document inputs/outputs and business rules without cluttering control flow. You’ll learn which artifacts improve understanding and which to omit for clarity.
- Execution semantics in Maestro
A quick mental model of token flow, concurrency, and error propagation so you can predict runtime behavior from the diagram and design for retries, timeouts, and compensations.
Imagine an Invoice Approval flow: a message start event receives an invoice, a user task captures approver input, an exclusive gateway routes invoices over a threshold to a second approver, and a service task posts the approved invoice to finance. A timer boundary event on the user task escalates if no action occurs within 48 hours, and an error end event records failures. Each symbol carries specific meaning; together, they make the process unambiguous for both reviewers and the automation engine.
