# Understanding Process implementation

> In Maestro, **implementation** is the step where a modeled process (your BPMN diagram) becomes an **executable, agentic workflow**. On the UiPath<sup>®</sup> 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](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/process-modeling-title) (designing the diagram) and from [Process operations](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/process-operations-title) (monitoring/running instances).

In Maestro, **implementation** is the step where a modeled process (your BPMN diagram) becomes an **executable, agentic workflow**. On the UiPath<sup>®</sup> 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](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/process-modeling-title) (designing the diagram) and from [Process operations](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/process-operations-title) (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

![implementation_scenario_purchase_request_approval](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-implementation-scenario-purchase-request-approval-617495-a0f5e349.webp)

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 &gt; 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.

Start importing a BPMN model, or drawing new one, or using [Autopilot for Maestro](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/autopilot-for-maestro) to help you along. See [Process modeling](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/process-modeling-title) for canvas features details.