Study guide

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

UiPath Automation Developer Professional UiPath-ADPv1

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Blueprint Map

1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan

2 Chapter 2: REFramework Architecture & State Dynamics

2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes

3 Chapter 3: REFramework Exception Handling & Recovery

3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination

4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing

4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues

5 Chapter 5: LINQ Queries & DataTable Operations

5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations

6 Chapter 6: Regex, DateTime, JSON & Invoke Activities

6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments

7 Chapter 7: Modern UI Automation & Unified Targeting

7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors

8 Chapter 8: Object Repository, Computer Vision & Remote Runtime

8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime

9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS

9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript

10 Chapter 10: Advanced Control Flow & Exception Architecture

10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures

11 Chapter 11: Orchestrator Queues & Transaction Management

11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers

12 Chapter 12: Orchestrator Tenant & Folder Entities

12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance

13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

14 Chapter 14: Monitoring, Recording & Solutions Management

14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources

15 Chapter 15: Debugging, Remote Debugging & Profiling

15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio

16 Chapter 16: RPA Testing & Test Suite

16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability

17 Chapter 17: Long-Running Workflows, Action Center & Apps

17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service

18 Chapter 18: Trigger-Based Attended Automation & Callouts

18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance

19 Chapter 19: UiPath Assistant & Robot Sessions

19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop

20 Chapter 20: Autopilot for Developers & Autopilot for Everyone

20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI

21 Chapter 21: API Automation & Integration Service

21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows

22 Chapter 22: Data Service, Context Grounding & Coded Workflows

22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services

23 Chapter 23: Integrated Scenario Practice

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

Key Takeaways Explain This Topic AI

Scenario questions combine topics; identify each requirement's topic and the rule that decides it.

Event triggers start work on arrival, queues distribute it, and Data Fabric keeps the auditable record.

Business rule exceptions are never retried; system exceptions retry through queue Auto Retry with the framework's MaxRetryNumber set to 0.

Human approvals belong in long-running coordinators with app or form tasks, not in performers.

Promotion relies on packages or solutions plus per-environment connections and assets, with monitoring, alerts, and recording in production.

Last updated: September 2026

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

Core Concept: Professional-level questions often describe a business scenario and ask for the best design across several topics at once. This section works through one integrated case, the kind of reasoning the exam expects, and connects each decision to the topic behind it.

The Scenario

A logistics company receives supplier invoices by email in a shared Microsoft 365 mailbox, about 3,000 per month, with peaks at month-end. Requirements:

Start processing soon after an invoice arrives.

Extract invoice data, check it against purchase orders in the ERP (desktop client, no API), and post approved invoices.

Invoices above 25,000 need a manager's approval with the option to change the approved amount.

Keep an auditable record of every invoice and its status.

Handle ERP outages without losing invoices; retry technical failures but never retry data problems.

Finance users ask questions such as "Why was invoice 4471 rejected?" in plain language.

Promote the solution from test to production without editing workflows.

A Reference Design

Requirement Design choice Topic

Start on arrival Integration Service event trigger "Email received" on the mailbox connection, filtered to messages with attachments; polling every five minutes by default Event triggers

Record keeping Data Fabric entities Invoice and Supplier, Status as a choice set, the PDF in a File field Data Fabric

Workload distribution Dispatcher creates Invoice records and adds each record Id to an Orchestrator queue ; a queue trigger scales performers Queues, triggers

ERP work REFramework performer with UI automation, Unified Target , and Object Repository descriptors from a shared library REFramework, UI automation

Data problems Throw BusinessRuleException ; set the item Failed with ErrorType Business , never retried Exceptions

ERP outages System exceptions retried through queue Auto Retry (MaxRetryNumber 0 in Config), MaxConsecutiveSystemExceptions to stop a job during an outage Retries

Approval A long-running coordinator uses Create App Task with an action app whose schema has an in/out ApprovedAmount and Approve and Reject outcomes, then Wait for App Task and Resume Long-running workflows, Apps

Questions in plain language A cross-platform automation for Autopilot for Everyone with a String input InvoiceNumber and a short ResultMessage Autopilot for Everyone

Promotion A solution or package deployed to test and production folders, with connections chosen through Package Requirements and environment values in assets Solutions, connections, assets

Monitoring Trigger alerts for stuck jobs, Monitoring > Queues , and recording of failed queue transactions Monitoring, recording

Why Not the Alternatives?

A time trigger every 5 minutes would start empty jobs; the event trigger starts only when mail arrives.

Keeping invoice data only in queue items loses a searchable history after processing; Data Fabric keeps the record, and the queue carries the Id. Queue items also have a Specific Data limit of 256,000 characters.

Retrying everything in the framework with MaxRetryNumber greater than 0 while also using queue Auto Retry would multiply attempts; with queues, the framework value must be 0.

A form task would work for simple approval, but the managers also need supplier history lookups during review, which an action app can provide through Integration Service or Data Fabric.

Waiting for approval inside the performer would hold a robot; the coordinator suspends instead.

Walking Through One Invoice

09:02 An email with INV-4471.pdf arrives. Within the polling interval, the event trigger starts the dispatcher.

The dispatcher saves the PDF to a new Invoice record ( Upload File to Record Field ), sets Status "Received", and adds a queue item with the record Id and Reference INV-4471 .

The queue trigger starts a performer. Get Transaction Item returns the item; the performer reads the record, extracts the data, and finds no matching purchase order.

It throws a BusinessRuleException "No PO found". SetTransactionStatus marks the item Failed (Business), and the Invoice record Status becomes "Rejected - No PO".

A finance user asks Autopilot "Why was invoice 4471 rejected?". The automation reads the record and returns "Rejected: no purchase order found for supplier ACME."

For an amount over 25,000, the performer instead sets Status "Awaiting approval", and the coordinator's app task handles the approval before posting.

Practice Questions for This Scenario

Use the design above to reason about the questions below. For each, identify the topic first, then the rule that decides the answer.

Which queue setting makes system exceptions retry automatically? ( Auto Retry with Max # of retries; framework MaxRetryNumber 0.)

What happens to an item whose robot crashed mid-processing? (It stays In Progress and becomes Abandoned after about 24 hours, then is retried only if abandoned items retry is enabled.)

How does the approval step avoid blocking a robot? ( Wait for App Task and Resume suspends the coordinator job.)

How do test and production use different mailboxes? ( Package Requirements select the connection per folder.)