BJSC MCQ key terms

A graphical model of a business workflow built in Process Studio, made of linked stages that control logic, data, and calls to business objects.

A reusable component built in Object Studio that exposes one application's actions and data to processes through a defined set of pages and actions.

A single symbol on a diagram, such as a decision, calculation, or action, that performs one defined step when the process runs.

The arrow connecting two stages that determines the order of execution and may carry conditions controlling whether the path is followed.

A named tab within a process or object that groups related stages; an object page holds the logic for one action.

A named, callable unit of work published by an object page, which a process invokes with inputs and receives outputs from.

The tool inside Object Studio where you describe an application's windows and elements so Blue Prism can identify and interact with them.

A saved definition of a window or control, with attributes and match settings, that an object uses to locate that target at runtime.

The properties of an element, such as name, class, or position, that Blue Prism compares against the live screen when searching for it.

A pointing tool in Application Modeller used to capture a window or control and generate its element definition automatically.

A named variable that stores a value of a declared data type and is visible to stages on the same page.

A data item holding a set of rows with named fields, commonly used to pass tables of work items or query results between stages.

A stage that evaluates one or more expressions and routes execution along the outgoing link whose condition is satisfied.

A stage that evaluates an expression and stores the result in a data item, often used for formatting, comparison, or simple transformation.

A stage that repeats the stages on its outgoing path for each row of a collection or until a specified condition is met.

A raised signal that normal processing cannot continue, which transfers control to the nearest recovery block or terminates the run.

A stage placed on a page that catches exceptions raised downstream, allowing the flow to handle the error and resume a defined path.

A stage that groups the stages on its outgoing path so they can be recovered as a unit if an exception occurs within them.

A block property that keeps the block's internal data items and stages available for inspection after the block completes or fails.

A failure caused by data or a business rule, such as an invalid invoice, that should be recorded and routed for human review rather than retried blindly.

A technical failure such as an application crash or timeout, usually handled by retrying, resetting the application, or marking the item deferred.

A managed list of items, each with data, status, and priority, that a process takes, processes, and marks complete or exceptional.

A single record in a queue, carrying key data and a status such as Pending, In Progress, Completed, or Exceptioned.

A queue item returned to the queue with a future retry time after a system exception, so it can be attempted again later.

A label attached to a queue item that records the outcome or reason for an exception, supporting filtering and reporting.

The web interface where administrators deploy processes, manage queues and schedules, monitor sessions, and review logs.

A running instance of a published process on a resource, which can be started manually or by a schedule and monitored in Control Room.

A machine or runtime environment registered with the platform that executes sessions and is assigned to a specific runtime licence.

A configured rule in Control Room that starts a session automatically at set times or intervals on a chosen resource.

A named value stored centrally and read at runtime, used to hold settings such as file paths or credentials without editing the process.

A secure store for usernames and passwords that processes retrieve at runtime, keeping secrets out of the model and its logs.

A standard starting structure for new processes that already contains common pages, error handling, and queue logic to enforce consistency.

A reusable starting structure for new objects that supplies standard pages and actions, such as launch, attach, and close, to speed development.

The design discipline of anticipating failures, catching them at the right level, and deciding whether to retry, defer, or escalate.

A controlled reattempt of a failed step or queue item, typically limited in number and paired with application recovery before resuming.

The step that releases a process or object version so it can be run from Control Room, replacing the previously published version.

The automatic recording of stage-level activity and exceptions that supports debugging, auditing, and reporting on a running session.

A formula written in the platform's syntax, using functions, operators, and data items, whose result is evaluated by a stage.