This session dives deep into the concepts of Agentic Orchestration, introduces BPMN-based design thinking, and shows how Maestro brings visibility, coordination, and scalability to agent-led workflows. If you’ve built an agent, this is where you learn to orchestrate it into a real-world process. Ideal for automation architects, solution designers, and anyone driving enterprise AI initiatives🙌🏻 Agenda: 👉What is Agentic Orchestration & Why It Matters 👉Introduction to BPMN 👉Meet UiPath Maestro: The Brain Behind the Flow 👉Core Components of an Agentic Workflow 👉Best Practices for Designing Scalable Orchestrations

1. 1
Agenda slide
01
02
03
BPMN/ Maestro Basics
Maestro Capability Across Lifecycle
Example Scenarios
04 Demo

2. 2
Orchestrate AI agents, robots, and
people to exceed business
outcomes.
• Adopt agents effortlessly into
processes
• Transform automation from
scattered tasks to seamless
workflows
• Simplify processes—and the way
you manage them

3. 3
Key features of UiPath Maestro
- Visual process modeling
- Unified Orchestration of Robots, Agents and People
- Real time monitoring and control
- Built in governance and security
- Seamless integration with UiPath Ecosystem
- Optimize with built in process insights

4. 4
Invoice to PO Matching Model
It’s time to Build

5. 5
How UiPath Maestro works across the
full process lifecycle
Model Implement Operate Monitor Optimize
Integrate agentic tasks, RPA,
human-in-the-loop, and API
events into your processes
Define business
decisions and rules,
ensuring consistent and
smart decision-making
with DMN
Design end-to-end
agentic processes using
industry- standard BPMN
constructs
Use Autopilot
to create
and edit BPMN and
DMN models using
natural language
Control specific
instances as they
progress through the
process
Obtain operational
analytics on your
orchestrated processes
in one place
Gain insight into
historical
instance
executions
Observe aggregated
process analytics
integrated into your
BPMN models
Improve processes by
eliminating
bottlenecks and
simulating multiple
scenarios
Understand the impact
of agents on top-level
KPIs by combining
process and task-level
data
Automation
s
Systems
Manual
Tasks
END-TO-END PROCESSES
AI
agents

6. 6
Definition
Activities are BPMN elements representing work performed in a process.
They can be manual or automated, consuming time, effort, or cost.
Activities move the process forward.
Types of Activities
Task – A single, indivisible step.
Sub-process – A group of tasks bundled together.
Call Activity – A reusable process invoked from outside.
Core Components of BPMN - Activities in BPMN

7. 7
1. Task
One clear action (manual or automated).
Already at the right level of detail.
Example: Approve request, send email, run script.
2. Sub-process
Mini-process inside the main workflow.
Organizes multiple tasks into neat layers.
Helps manage complexity.
3. Call Activity
Wrapper that triggers another independent BPMN process.
Makes processes reusable across diagrams.
Example: Standard approval workflow used in multiple processes.
Core Components of BPMN - Activities in BPMN

8. 8
Definition
An event is represented by a circle symbol.
It marks something happening in the process (not actual work being performed).
Events guide when and how a process starts, reacts, or ends.
Types of Events
Start Events → Trigger the beginning.
Intermediate Events → Occur in the middle, influence the flow.
End Events → Mark completion of the process.
Core Components of BPMN - Events in BPMN

9. 9
Start Events
Occur at the beginning.
Symbol: Circle with a thin line.
Every process must start with one.
Intermediate Events
Happen between activities.
Symbol: Circle with a double line.
Do not start or end a process, but affect the flow.
Two kinds:
• Throwing events → Produce signals/messages.
• Catching events → Listen/wait for signals.
Core Components of BPMN - Types of Events

10. 10
End Events
Occur at the end.
Symbol: Circle with a thick line.
Every process has at least one.
Core Components of BPMN - Types of Events

11. 11
Define Clear Process Scope
Clarify the 5 Ws – Who, What, When, Where, Why.
Identify discrete process instances for tracking.
Always use Start and End Events to show triggers & outcomes.
Maintain Consistent & Readable Layouts
Aim for one-page diagrams for clarity.
Minimize crossing flows.
Keep flow directions consistent (horizontal for sequence, vertical for data).
Avoid zigzag paths – highlight the Happy Path clearly.
Externalize complex rules with Business Rule Tasks.
Tailor visualizations for stakeholders:
• Executives → summary with collapsed sub-processes.
• Technical teams → detailed diagrams with expanded sub-processes.
Best Practices for BPMN 2.0 Modeling

12. 12
Structure Processes Hierarchically
Use Sub-processes to simplify complexity.
Apply Call Activities for modularity & reusability.
Proper Use of Start & End Events
Always include Start and End Events.
Use separate Start Events for different triggers (form, API, update).
Model distinct End Events for different outcomes.
Merge flows with the same outcome into one End Event.
Effective Use of Gateways
Clearly depict decision points.
Avoid mixed gateways (splits + joins in one).
Place a decision activity before diverging gateways.
Use Business Rule Tasks to simplify complex logic.
Best Practices for BPMN 2.0 Modeling

13. 13
🚩 Overcomplicating the Model
Keep it simple – avoid unnecessary detail.
Focus only on key activities and decisions for clarity.
🚩 Inadequate Naming Conventions
Use descriptive labels for events & activities.
Avoid vague terms like “Start” or “End”; specify triggers/outcomes clearly.
🚩 Misusing Gateways
Always choose the right type (exclusive, inclusive, parallel).
Avoid inserting gateways where no real decision/parallelism exists.
Red Flags to Avoid

14. 14
🚩 Neglecting Error Handling
Model potential exceptions & errors with boundary events.
Helps handle unexpected scenarios gracefully.
🚩 Inconsistent Use of Pools & Lanes
Use pools & lanes to define participants/departments.
Every activity should belong to a specific lane—never between lanes.
🚩 Ignoring Sequence Flow Direction
Maintain a logical, consistent flow of activities.
Avoid loops, backward arrows, or ambiguous paths.
Red Flags to Avoid

15. Demo