- 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
Configure non-interrupting boundary message events in Maestro to process updates while a task is in progress without halting the main workflow.
Handle updates without interrupting work (non‑interrupting boundary messages)
Use when
- You need to process updates while a task is in progress.
- Updates should not halt the main work.
Pattern in simple words
- Start.
- Subprocess: Deliverable preparation.
- Non‑interrupting boundary message Updated requirements received: User task Log new requirements. Service task Adjust project plan. End Requirements handled.
- Non‑interrupting boundary message Compliance rule change received: User task Review rule change. Service task Update compliance checklist. End Compliance handled.
- Main path: Deliverable preparation completes. End Deliverable completed.
Result
The main task runs to completion while each non-interrupting boundary message spawns an independent side flow that handles the update without stopping the primary work.
Each message triggers a small side flow without stopping the main work.
Other scenarios
- Finance: Credit‑risk review receiving new market data.
- Healthcare: Care‑plan preparation receiving updated lab results.
- Manufacturing: Product design updates from regulation changes.
- Retail: Campaign plan updates with product revisions.
- Telecom: Network upgrade planning updates with compliance changes.
Cancel during a task (interrupting message)
Use when
- Work must stop immediately on a cancel request.
- A clear message should abort the task.
Pattern in simple words
- Start.
- Subprocess: Process booking.
- Interrupting boundary message Cancel request: User task Stop and notify. End Cancelled.
- Normal path: Process booking completes. End Completed.
Result
The interrupting boundary message immediately cancels the active subprocess and the work stops cleanly, while the normal completion path is followed when no cancellation message arrives.
The interrupting message cancels the active work at the subprocess boundary.
Other scenarios
- Finance: Loan withdrawal cancels underwriting.
- Healthcare: Patient cancels a scheduled procedure.
- Manufacturing: Cancel production order before run.
- Retail: Cancel order before shipment.
- Telecom: Cancel new service setup.
Event‑driven dispatcher (message start)
Use when
- A new external message should start a process.
- Each event spawns an independent workflow instance.
Pattern in simple words
- Message start: New email received.
- Service task: Create support ticket.
- Send task: Confirm receipt.
- End Ticket created.
Result
Each incoming message starts a new independent workflow instance, a support ticket is created, and a confirmation is sent to the originator.
Each incoming message creates a new instance.
Other scenarios
- Finance: Vendor request message starts onboarding.
- Healthcare: Referral message starts patient intake.
- Manufacturing: Defect report starts QA process.
- Retail: Online order starts fulfillment.
- Public sector: Citizen inquiry opens a case record.