- 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
Process implementation in Maestro: converting a BPMN model into an executable agentic workflow with runtime instructions, variables, and automation bindings.
In Maestro, implementation is the step where a modeled process (your BPMN diagram) becomes an executable, agentic workflow.
On the UiPath® Studio Web canvas, you add runtime instructions (properties, variables/expressions, events, tasks, and gateways), bind them to automations, AI agents, and human steps, then test and publish to the process engine.
This stage is distinct from Process modeling (designing the diagram) and from Process operations (monitoring/running instances).
Why it matters: Maestro’s implementation stage is where the orchestration across robots, AI agents, and people is defined so the process can actually run end‑to‑end.
A simple implementation example
Use case: Purchase request approval
The example process contains the following elements:
- Variables —
Amount:numberandRequesterEmail:string(Expression editor) drive routing and outbound notifications. - User task —
Manager review, assigned to the Manager role, captures the approval decision. - Exclusive gateway — evaluates
Amount > 5000and routes toCFO approvalif true, or directly to fulfillment otherwise. - Service task — calls an external system or automation to create a purchase order.
- Send task — emails
Request approved / rejectedtoRequesterEmail. - Timer event — on
Manager review, escalates after 24 hours via an alternate path. - Test & publish — the solution is validated with Simulate/Debug, then published to make the process available.
This example provides you clear routing by amount, auditable approvals, automatic PO creation, and notifications—implemented once, reused safely.
Start importing a BPMN model, or drawing new one, or using Autopilot for Maestro to help you along. See Process modeling for canvas features details.