Blue Prism Developer key terms

An ordered diagram of stages that automates one business task from start to finish, built in Process Studio and run by a robot at a scheduled or manual time.

A reusable component built in Object Studio that exposes actions for interacting with one application, such as a browser, terminal, or desktop program. Processes call its actions instead of duplicating interface logic.

A Blue Prism object whose actions model meaningful business operations on an application, for example logging in or retrieving a customer record, so processes stay independent of interface detail.

The design surface where developers build, debug, and run processes. It provides stages, data items, decision routing, and step-through execution for testing logic before publishing.

The design surface used to build objects. It supplies application modelling, action pages, and read/write stages so developers can wrap an application's interface into callable, reusable actions.

A single building block placed on a page, such as Action, Decision, Calculation, Data, Read, Write, Navigate, or Multi-Calc. Stages are linked by links that determine execution order.

A named tab within a process or object that holds its own stages, links, and data items. Pages can be called from other pages and help organise large automations into manageable units.

The default entry page created with every process or object. Execution begins here, and its data items are visible to pages it calls unless scoped more narrowly.

The arrow connecting one stage to the next, defining the path execution follows. Decision stages use multiple outgoing links, each carrying a condition that must be true to be taken.

A named variable that stores a value during execution, with a defined data type and optional initial value. Scope determines whether it is visible only on its page or across the whole process.

The classification of a data item, such as Text, Number, Date, Time, Flag, or Collection. The type restricts what values can be stored and which functions and comparisons are valid.

A structured data type holding rows and fields, similar to a table. Collections store lists of work items or query results and support field access, filtering, and looping through rows.

A branching stage that evaluates one or more conditions on outgoing links and routes execution down the first link whose condition is true, enabling if/else and case logic.

A stage that evaluates an expression and stores the result in a data item, or evaluates a condition without storing it. It performs arithmetic, text manipulation, date maths, and function calls.

A stage in a process that calls a named action on an object, passing input parameters and receiving outputs. It is the main way processes reuse interface logic held in objects.

A callable unit inside an object, implemented on a page, that accepts inputs, performs interface work, and returns outputs. Processes invoke actions through action stages.

The tool inside Object Studio for describing an application's windows and controls so stages can identify and interact with them. It stores element definitions and matching attributes used at runtime.

A saved definition of a window or control in the Application Modeller, holding match attributes and a path. Stages reference elements by name rather than hard-coded screen positions.

A capture facility that identifies a control in a running application and creates or updates an application element by recording its hierarchy and match attributes.

The properties of a control, such as name, class, or text, that Blue Prism compares at runtime to confirm it has found the correct element. Matching uses wildcards and selected attributes.

An object stage that extracts a value from an application element, for example reading text from a field or cell, and places it into an output data item.

An object stage that sends a value to an application element, such as typing into a text box or setting a checkbox, using the element definition to locate the target control.

An object stage that performs interface actions on an element, such as clicking, pressing keys, or focusing a control, to move the application into the required state.

A stage that pauses execution until a condition is met, such as an element appearing or a window title matching. It replaces fixed delays and makes automation resilient to timing variation.

An error or unexpected condition raised during execution. Exceptions interrupt the current path and are handled by recovery logic, retry, or escalation rather than silently ignored.

The design pattern of blocks, recover stages, and resume stages that catches errors, decides whether to retry or fail, and returns execution to a defined point in the process.

A stage that marks the end of a block's normal path and the start of its recovery path. Execution jumps here when an exception occurs inside the associated block.

A stage that ends a recovery path and returns execution to the block's next stage after the block, or to a specified stage, allowing the process to continue after handling an error.

A grouped section of a diagram, bounded by a block stage and a recover stage, that can be treated as a unit for exception handling and for retry logic.

A central list of work items that robots pull from, providing status tracking, priority, tags, and deferred or exception states so multiple robots can share workload without duplication.

A single record in a work queue, carrying key data and a status such as Pending, In Progress, Completed, or Exception. Each item is normally processed by one robot session.

The lifecycle state of a work item, including Pending, In Progress, Completed, Exception, and Deferred. Status drives reporting and determines which items are available to robots.

A work item deliberately postponed until a future date and time, for example when a dependency is not yet ready. It returns to Pending automatically when its deferral expires.

The operational console where administrators manage processes, objects, queues, schedules, and sessions, start or stop robots, and review logs and performance across the digital workforce.

A single running instance of a process on a resource, with its own status, logs, and runtime data. Control Room shows active and completed sessions for monitoring and troubleshooting.

A runtime environment, typically a machine with a Blue Prism interactive client, on which sessions execute. Resources are assigned to groups that determine which processes they may run.

A configured rule that starts a process on a resource at set times or intervals, with optional calendars and repeat settings. Schedules let routine automation run without manual starts.

A named value stored centrally and read at runtime, used to hold configuration such as file paths, credentials references, or queue names that differ between environments without editing processes.

A securely stored username and password pair, managed centrally and referenced by name at runtime so secrets are not hard-coded in processes or visible in logs.