AA Master RPA key terms

The centralized web-based management console in Automation Anywhere that stores bots, schedules tasks, manages users and roles, and monitors activity across the enterprise. It is the hub for deployment and governance.

A licensed user role that builds and edits bots using the development client. Creators can design automation logic but typically cannot run production workloads or manage the Control Room configuration.

A licensed user or machine that executes bots rather than authoring them. Runners are assigned to devices and consume runtime capacity when tasks are scheduled or triggered.

The local service installed on a device that connects it to the Control Room and executes assigned automations. It authenticates the device, receives tasks, and reports execution status back to the server.

A bot built to perform a specific, often linear sequence of steps such as data entry or file processing. Task bots are the most common building block and can be called by other bots.

A reusable bot that exposes callable actions consumed by other bots, similar to a function library. It promotes modular design so shared logic is maintained in one place and invoked many times.

A development tool that captures a user's on-screen actions such as clicks and keystrokes and converts them into automation steps. Recordings are usually refined manually afterward.

A capture technique that identifies UI elements by their underlying properties rather than screen coordinates, producing more resilient automation that survives layout changes and window resizing.

A set of attribute-value pairs that uniquely locate a screen element at runtime, such as window title, control name, or class. Reliable selectors are central to stable UI automation.

A named container that holds a value during bot execution, such as text, numbers, or lists. Variables pass data between actions and enable dynamic behavior instead of hard-coded values.

A structured variable holding key-value pairs, useful for looking up values by name and representing records or configuration sets. It supports iteration and nested access within automation logic.

An action that assigns, copies, or manipulates variable values during execution, including arithmetic, string handling, and type conversion. It is the primary way bots transform data between steps.

A control construct that repeats a set of actions until a condition is met or a collection is exhausted. Common forms include fixed-count loops, condition loops, and iteration over lists or files.

Logic that executes a block of actions only when a specified expression evaluates true, using if/else branching. It lets bots handle varied inputs and make decisions without human intervention.

A structured block that catches exceptions raised during bot execution and defines recovery steps such as logging, retrying, or cleanup. It prevents an unhandled failure from aborting the whole task.

A pattern wrapping risky actions in a guarded block so that failures are caught and handled rather than terminating execution. The catch branch defines the response to the captured exception.

An unexpected condition raised at runtime, such as a missing file, failed login, or unresponsive application. Bots must anticipate exceptions and define handling so processes degrade gracefully.

A design pattern that re-attempts a failed action a set number of times, often with a delay, before escalating. It absorbs transient faults like slow pages or temporary network errors.

A secure store in the Control Room that holds usernames, passwords, and other secrets, letting bots retrieve them at runtime without hard-coding sensitive values in automation logic.

A permission model that grants users capabilities according to assigned roles, such as creator, runner, or administrator. It limits who can build, execute, or administer automation assets.

A chronological record of user and system activity in the Control Room, capturing who did what and when. It supports compliance reviews, troubleshooting, and investigation of security incidents.

A Control Room feature that runs bots at defined times or intervals, optionally on selected devices and with parameters. It enables unattended automation without manual triggering.

Execution of bots without a human present, typically on dedicated machines or virtual desktops. It suits high-volume, scheduled work and requires robust error handling and monitoring.

Execution of bots triggered by a human user on demand, often on the same desktop, to assist with a task in progress. It blends human judgment with automated steps.

A work item store in the Control Room that holds records to be processed by bots, supporting status tracking and load distribution. Queues decouple data intake from processing capacity.

A single record within a queue representing one unit of work, carrying data and a status such as new, in progress, or completed. Bots lock and process items to avoid duplication.

One complete unit of processing within a bot run, often corresponding to a work item or record. Transaction-level error handling allows one failure to be isolated without stopping the batch.

A self-contained piece of automation logic packaged for use across multiple bots, reducing duplication and simplifying maintenance. Changes made once propagate to every consumer.

A relationship where one bot relies on another bot, file, or external system to function. Dependencies must be tracked and deployed together to avoid runtime failures.

The process of moving a bot from a development environment into test or production, including packaging, dependency checks, and configuration. Controlled deployment reduces risk of production incidents.

Practice of tracking changes to bot artifacts so prior versions can be reviewed or restored. It supports collaboration, rollback after defects, and auditability of automation changes.

A dedicated team that sets standards, provides tooling and training, and governs the RPA program across the organization. It drives reuse, quality, and scaling of automation initiatives.

The policies, roles, and controls that direct how automation is proposed, built, approved, and operated. Good governance balances speed of delivery with security, compliance, and maintainability.

A prioritized backlog of candidate processes assessed for automation suitability, often scored by volume, rule-based nature, and stability. It guides which opportunities the program tackles next.

The activity of identifying and documenting candidate processes for automation, capturing steps, systems, exceptions, and volumes. Accurate discovery prevents automating poorly understood or unstable work.

The end-to-end stages a bot passes through: requirements, design, development, testing, deployment, operation, and retirement. Managing each stage ensures quality and sustained value.

The practice of recording bot events, decisions, and errors to a file or system during execution. Logs support troubleshooting, performance analysis, and compliance evidence.

The set of steps a bot takes after a failure to restore a consistent state, such as closing applications, releasing locks, or reverting partial changes. It keeps subsequent runs reliable.