ExamFinch.com My Study

Study guide

17.3 UiPath Apps: Action Apps, Automations & Integration Service

Practice this exam

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

17.3 UiPath Apps: Action Apps, Automations & Integration Service

Key Takeaways Explain This Topic AI

Apps combine pages, controls, rules, referenced Orchestrator processes, and Integration Service connections.

An app can call several focused automations, passing inputs from controls and binding outputs back.

An action app has one Action control whose schema holds input, output, and in/out properties and outcomes (one input and one Submit outcome by default).

Outcomes are mapped to Submit Action rules; the app is published and deployed to an Orchestrator folder.

Create App Task and Wait for App Task and Resume use the action app as the task interface in Action Center; Coded Action Apps use React or Angular.

Last updated: September 2026

17.3 UiPath Apps: Action Apps, Automations & Integration Service

Core Concept: UiPath Apps builds web interfaces for automations, without writing front-end code. The exam description lists advanced Apps topics: action apps with their action schema , apps that call multiple automations , and apps that use Integration Service APIs. Apps are built in Studio Web (app projects) or UiPath Apps Studio.

What an App Is Made Of

Part Role

Pages and controls The interface: text boxes, dropdowns, date pickers, buttons, tables, edit grids, tabs, containers, file upload, and more

Rules Logic attached to control events, such as a button's Click event: set values, navigate, run automations, or submit an action

  • Referenced automations Orchestrator processes the app can start, passing input arguments and reading outputs
  • Connections Integration Service connections that let the app call application APIs directly
  • Variables and expressions Values shared across pages and controls
  • Apps and Automations

An app can reference several processes , each doing part of the work. A customer service app might:

Run a lookup process when the agent enters an account number, filling a table with the output.

Run an update process when the agent edits details and selects Save.

Run a document process that generates a letter.

Each call passes input arguments from controls and returns output arguments that the app binds to controls. Keeping the processes small and focused makes the app responsive and each automation reusable.

Apps can also use Integration Service connectors directly, for example to read records from a CRM, without a process in between. Use a process when the logic needs UI automation or complex steps, and a connector call for simple API reads and writes.

Action Apps

An action app is an app used as the interface of a task in Action Center . It replaces a form task when you need a richer interface.

Building an action app

Add an Action control to the app (via Add control ). Only one action per app is allowed. Once deployed, the app is opened through Action Center.

The Action Properties schema opens. It starts with one input property and one Submit outcome .

Add properties of the kinds you need:

Input: data the workflow sends to the task.

Output: data the reviewer returns.

In/Out: data sent to the task that the reviewer can change.

Property names must follow VB naming conventions, you can mark properties required, and complex types such as objects support sub-properties.

Map inputs and in/out properties to input controls . A required input or in/out property should be mapped to an input control.

Add outcomes such as Approve and Reject. Each outcome is mapped to a Submit Action rule, typically on a button's Click event.

Publish the app, then deploy it to an Orchestrator folder (Automations > Apps > Deploy app).

Using it from a workflow

In a long-running workflow, Create App Task creates the task with a title, priority ( TaskPriority.Low , Medium , High , or Critical ), the deployed action app, and values for the schema's properties. Wait for App Task and Resume suspends the job until the reviewer submits an outcome, then returns the task data, including outputs and the chosen outcome.

The action app can also be a Coded Action App , a custom React or Angular application built in your own IDE.

Action App Versus Form Task

  • Form task Action app task
  • Designer Form designer in Studio Apps (Studio Web or Apps Studio), or code
  • Interface Form components Full app pages, rules, and controls
  • Data contract Form data (In, Out, In/Out) Action schema properties and outcomes
  • Activities Create Form Task, Wait for Form Task and Resume Create App Task, Wait for App Task and Resume
  • Best for Simple reviews and data entry Rich reviews, lookups during review, reuse across processes
  • Worked Example: Credit Limit Approval

The action app's schema has inputs CustomerName and RequestedLimit , an in/out property ApprovedLimit , and an output Comment , with outcomes Approve and Reject .

The app shows the customer's history by calling an Integration Service connector for the CRM when the page loads.

A long-running process runs Create App Task with the request values and then Wait for App Task and Resume .

The reviewer lowers ApprovedLimit , adds a comment, and selects Approve , which runs the Submit Action rule with that outcome.

The process resumes, reads the outcome and ApprovedLimit , and updates the ERP.

Common Traps

Only one Action control per app.

An outcome only works when mapped to a Submit Action rule.

An action app must be deployed to an Orchestrator folder before Create App Task can use it.

Required input and in/out properties need input controls.