AA Master RPA flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Control Room

Central web console for managing users, roles, bots, devices, credentials, and schedules; it coordinates automation but does not execute bot logic itself.

Bot Creator

Licensed development environment where users design, edit, and test bots before checking them into the Control Room repository.

Bot Runner

Licensed runtime component that executes bots on a device; consumes a runtime license and connects to Control Room.

Credential Vault

Encrypted store for credentials and lockers; bots retrieve secrets at runtime without exposing plaintext in bot logic.

Attended automation

Bot execution triggered by a user action on the desktop; the bot assists the user in real time rather than running unattended.

Unattended automation

Bot execution without a logged-in user, typically scheduled or queue-driven on a dedicated Bot Runner device.

Audit log

Record of user and bot actions with timestamps; used for compliance, troubleshooting, and change tracking in Control Room.

Action

Building block of a bot with input parameters, output variables, and optional error handling; represents a single operation.

Variable declaration

Process of defining a variable's name and type (string, number, boolean, list, dictionary, record) before use in a bot.

Recorder

Tool that captures user UI interactions into actions; recorded steps should be reviewed and parameterized for reuse.

Selector

Set of attributes (name, class, control type) that identifies a UI element; stable selectors improve bot resilience across sessions.

If/Else action

Control-flow action that executes one branch when a condition is true and another branch when false.

Loop action

Control-flow action that repeats a set of steps a fixed number of times or until a condition is met.

Log To File

Action that writes messages to a log file; used for debugging and operational traceability of bot execution.

Wait For Condition

Action that pauses execution until a specified condition is true, preferred over fixed delays for synchronization.

Bot export package

File containing a bot and its dependencies for import into another Control Room; verify version compatibility before importing.

Parent-child architecture

Design where a parent bot orchestrates child bots via Run Task, passing input and output variables between them.

Try/Catch/Finally

Error-handling structure that isolates failure-prone steps, handles exceptions in Catch, and runs cleanup in Finally.

On Error action

Action that defines bot behavior on failure: resume next, go to a label, or terminate the bot.

Retry logic

Pattern using a counter and delay to reattempt transient failures; retries should be capped to prevent infinite loops.

Idempotency

Design property ensuring re-running a failed bot instance does not duplicate transactions; enforced with unique keys and status checks.

Work item queue

Mechanism to enqueue units of work with statuses (new, in progress, completed, failed) for distribution across Bot Runners.

Centralized logging

Convention of recording timestamp, bot name, step, severity, and message to a central location for cross-bot troubleshooting.

Configuration externalization

Practice of storing URLs, paths, and thresholds in config files or Control Room stores instead of hardcoding them in actions.

Deployment lifecycle

Sequence of developing in Bot Creator, checking into repository, deploying to Bot Runners, then scheduling or triggering execution.

Schedule

Control Room definition of when a bot runs (once, daily, weekly, cron-like), assigned to devices or device pools.

Device pool

Group of Bot Runners used for load balancing; queued tasks are distributed to available devices in the pool.

Role-based access control

Assigning least-privilege roles such as Bot Developer, Bot Runner, or Administrator to users and groups in Control Room.

Version control

Repository feature using check-in with comments and version history; enables rollback to a prior bot version if needed.

Deployment checklist

Pre-go-live validation of bot dependencies, credentials, device availability, schedule conflicts, and rollback plan.

Center of Excellence

Organizational function that defines standards, reusable components, review gates, and training for bot development.

Segregation of duties

Control ensuring developers do not have production deployment rights without a separate approver, reducing unauthorized changes.

Bot lifecycle governance

Maintaining an inventory of bots with owner, purpose, risk rating, and review date; retiring unused bots to reduce risk.