Understanding Process implementation

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 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

1. Create Variables: Amount:number, RequesterEmail:string (Expression editor).
2. Add a User task Manager review assigned to the Manager role.
3. Add an Exclusive gateway. Amount > 5000? routes to CFO approval if true, otherwise straight to fulfillment.
4. Add a Service task. Call an external system/automation to create a PO (placeholder connector/automation).
5. Add a Send task. Email Request approved / rejected to RequesterEmail.
6. Add an Event. Add a timer on Manager review: escalate after 24h with an alternate path.
7. Test & publish – run Simulate/Debug, then Publish the solution to make the process available.

This example provides you clear routing by amount, auditable approvals, automatic PO creation, and notifications—implemented once, reused safely.

Commencez par importer un modèle BPMN ou à en dessiner un nouveau, ou à utiliser Autopilot™ pour Maestro pour vous aider. Voir la section Modélisation des processus pour obtenir des informations détaillées sur les fonctionnalités du canevas.