ExamFinch.com My Study

Study guide

18.3 Callouts & Forms for Attended Guidance

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

18.3 Callouts & Forms for Attended Guidance

Key Takeaways Explain This Topic AI

A callout is a uiform form bound to a UI element and displayed next to it with Show Callout.

Callouts can also be handled with Form.Activities because they are uiform files.

Show Callout passes values to the callout's components, and Instance Name distinguishes several visible callouts or forms.

Callout button events are handled with Form Event Trigger workflows in a Run Local Triggers design.

Keep callouts short, attached to stable elements, and closed when no longer relevant.

Last updated: September 2026

18.3 Callouts & Forms for Attended Guidance

Core Concept: A callout is a form bound to a UI element and displayed next to it. Callouts guide users inside the applications they already use: they point to the right field, validate input, pre-fill values, or start automations from a button. The exam description lists callouts among attended automation topics.

What a Callout Is

A callout is a .uiform file designed with the Form Builder , like any form.

The Show Callout activity (Callout.Activities package) displays it next to an indicated UI element in an application, website, or form.

Because callouts are uiform files, they can also be handled with the Form.Activities package, just like regular forms.

  • Form Callout
  • Position A window of its own Anchored next to a UI element
  • Typical use Collect or show larger amounts of information Short hints, validations, and buttons in context
  • Activity to show it Show Form Show Callout
  • Show Callout Essentials
  • Property Purpose
  • Target The UI element the callout attaches to
  • Callout (uiform) file The callout to display
  • Arguments A dictionary of values passed to the callout's components, for example the value to show in a label
  • Instance Name A unique name so that several callouts or forms can be shown and addressed separately

Values set through Arguments fill the callout's components when it opens. Components such as buttons can raise events that a Form Event Trigger workflow handles.

Common Callout Patterns

Guidance: point at a field the user often gets wrong, with a short explanation.

Validation: when the user leaves a field, a trigger workflow checks the value and shows a callout if it is invalid, for example "Policy number must have 10 digits".

Pre-filling: a callout offers a suggested value with a "Use this value" button that fills the field.

Starting automations: a callout button such as "Create refund" starts a trigger workflow that does the work in the background.

AI summaries: a callout shows a short summary produced by a GenAI activity next to a long record.

Wiring a Callout into Trigger-Based Automation

A typical validation flow:

The main workflow runs Run Local Triggers .

A trigger workflow starts with an Application Event Trigger for the Focus lost event of the "Policy number" field, found with the Event Inspection Tool.

The workflow reads the field value and checks it.

If the value is invalid, Show Callout displays PolicyHint.uiform next to the field, passing the message through Arguments .

A Form Event Trigger on the callout's "Fix it" button formats the number and writes it back.

Designing Good Callouts

Keep them short. One message and at most one or two buttons.

Attach to stable elements. Use reliable, strict selectors for the target, because a callout that appears in the wrong place confuses users.

Use Instance Names when more than one callout or form can be visible.

Close them deliberately. Close the callout when the user fixes the value or moves to another screen, so stale callouts do not pile up.

Test in the real application. Screen scaling and window positions affect where the callout appears.

Forms Recap for Attended Scenarios

Forms and callouts share the Form Builder and many activities:

  • Activity Use
  • Show Form / Show Callout Display a form or a callout
  • Get Form Values / Set Form Values Read or change values at run time
  • Change Form Properties Change properties such as title or size at run time
  • Run Form Script Run custom JavaScript in the form
  • Close Form Close a form instance
  • Form Event Trigger Start a workflow on a form or callout event
  • Worked Example: Refund Approval Hint

A service agent issues refunds in a web back office. The automation:

Watches the refund amount field with a trigger workflow.

When the amount exceeds the agent's approval limit, shows a callout next to the Submit button: "Amounts above your limit need supervisor approval".

The callout offers Request approval , which starts a workflow that creates an approval task and records its ID in the ticket.

The callout closes once the request is sent.

The agent stays in the back office the whole time, and the rule is enforced where the mistake would happen.

Common Traps

A callout is not a separate application window; it needs a target UI element .

Callout events are handled by Form Event Trigger workflows, not by polling.

Forgetting unique Instance Names makes it hard to update or close the right callout.

Showing callouts from a workflow that does not run triggers; the callout's buttons then have no Form Event Trigger listening.