UIADP key terms

A bot that runs on a person's own workstation and is started by that user or by a trigger, sharing the desktop with them in real time while they work.

A bot that runs with nobody present, usually launched from Orchestrator on a dedicated machine, working through batches of items or running on a schedule.

A design pattern in which the automation pauses and asks a person to review, approve, or supply missing data before the process continues.

Analysis of system event logs or recorded user actions to discover how a business process actually runs, so automation candidates can be identified and measured.

A Studio container that runs its activities one after another in a fixed order; best suited to short, linear steps with little or no branching.

A Studio container that connects activities with arrows and decision nodes, allowing branching, loops, and jumps back to earlier steps in the workflow.

A Studio container built from states and transitions, where the process moves between named states when conditions are met; suited to complex, event-driven workflows.

A reusable package of workflows published to a feed and consumed by other projects, so common logic is built once and shared across automations.

An external package that a project references, such as an activity library or your own component, downloaded and version-controlled through Manage Packages.

A named container inside a workflow that holds a value of a declared type and is scoped to the container where it is defined, such as one sequence or the whole file.

A value passed into or out of a workflow in an In, Out, or In/Out direction, letting the same workflow file be reused with different inputs and outputs.

An in-memory table of rows and columns where each column has a data type; the standard structure for handling spreadsheet, CSV, and database records.

A collection of key-value pairs in which every key is unique and maps to exactly one value, giving fast lookup by key instead of by position.

A UiPath data type able to hold any kind of value, such as text, number, date, or boolean, converting automatically; convenient but slower and less type-safe.

A text pattern used to find, validate, or extract parts of a string, applied in UiPath through activities such as Is Match, Matches, and Replace.

An XML string that tells UiPath which user interface element to act on, assembled from attributes such as name, id, and class plus the surrounding window hierarchy.

A selector in which * matches any number of characters and ? matches exactly one, so attributes that change at runtime, like IDs or titles, still match.

A container that first locates a stable element, the anchor, and then finds the target relative to it, used when the target's own attributes are unreliable.

A Studio tool for inspecting a running application's element tree and building or repairing selectors by picking attributes and validating the highlighted target.

Input methods that send commands straight to the target window instead of driving the physical mouse or keyboard, so they are faster and work without focus.

An activity that opens a workbook through the Excel interop and exposes Excel activities inside it, keeping the file open until the scope ends.

An activity that loads a worksheet range into a DataTable; the starting cell can be left empty to read the used range, and headers may be included.

An email protocol used by the IMAP and Get IMAP Mail Messages activities to read mail from a server, with no desktop mail client required on the robot machine.

Activities that drive an installed Outlook desktop client through its existing profile, allowing read, send, and move operations without configuring server credentials.

A marker placed on a workflow line that pauses execution when reached, so you can inspect variable values and step through the logic that follows.

A container that runs a guarded block, then routes any exception to the first matching Catch block, and optionally runs a Finally block whatever the outcome.

A container that repeats its body until a condition is true or a maximum number of attempts or time limit is reached, useful for unreliable UI actions.

An exception type signalling that an item breaks a business rule, such as invalid data or missing approval, rather than a technical fault; the item is not retried.

A project-level handler that catches exceptions not dealt with locally, letting you log details, take a screenshot, and decide whether to continue or stop.

A server-side list of work items that robots add and consume one at a time, tracking status, retries, and references so no item is lost or duplicated.

A named value stored in Orchestrator, such as text, number, boolean, or credential, that a robot reads at runtime so settings and passwords live outside the workflow.

A schedule or event configured in Orchestrator that starts a process on a machine at a chosen time or interval without a person launching it.

A container in Orchestrator that groups processes, queues, assets, and the users and robots allowed to use them, separating environments, departments, or teams.

UiPath's template for complex business processes, built as a state machine that initializes settings, fetches transactions, processes each one, and handles errors with retries and logging.

A single unit of work, usually a queue item, holding a content payload, a reference, a status, and a retry count, processed once by one robot.

The settings workbook read by InitAllSettings in REFramework, holding asset names, queue names, and constants that the process uses at runtime.

A REFramework workflow that sets a transaction's final queue status to Successful, Business Exception, or Application Exception and records the reason.

A saved snapshot of staged changes in a local Git repository, carrying a message and author, that becomes one point in the project's history.

The Studio action that packs a project into a NuGet package and sends it to Orchestrator or another feed, making that exact version available to run.

Automated build, test, and deployment steps that take committed automation code and deliver a tested package to Orchestrator with little or no manual work.