BJSC MCQ flashcards

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

Process Studio vs Object Studio

Process Studio builds orchestration logic and business flow. Object Studio builds reusable application interactions (Actions) against a modelled application. Processes call Object Actions.

What is a Session

A Session is a single running instance of a published Process or Object, started from the Control Room or a Schedule, executed on a Resource.

Data Item vs Collection

A Data Item stores a single typed value. A Collection stores tabular rows with named fields, used for queue-like or list processing.

Environment Variables purpose

Environment Variables store configuration values that differ per environment, so the same Process or Object can run unchanged across dev, test, and production.

Stage types overview

Stages include Action, Decision, Choice, Calculation, Data, Collection, Loop, Block, Page, Read, Write, Navigate, Wait, and Exception. Each performs a defined function.

Control Room role

The Control Room manages Resources, Sessions, Queues, and Schedules. It starts and monitors Sessions and tracks queue item states across the environment.

Decision stage behaviour

A Decision stage evaluates Boolean expressions on outgoing links. Execution follows the first link whose expression is true; design a fallback to avoid exceptions.

Choice stage behaviour

A Choice stage evaluates one expression and routes to an outcome matching its value. Each outcome is a named link with a corresponding value.

Loop stage over Collection

A Loop stage iterates each row of a Collection. Inside the loop, field names reference the current row's values for calculations and actions.

Block stage links

A Block stage scopes stages. The Recover link runs when an exception occurs inside the block; the Resume link runs when the block completes successfully.

Page stage reuse

A Page stage groups related stages into a reusable sub-flow. Pages improve readability and allow the same logic to be called from multiple places.

Calculation stage use

A Calculation stage evaluates an expression and stores the result in a Data Item. It handles arithmetic, string concatenation, and built-in function calls.

Link conditions

Link conditions are Boolean expressions attached to outgoing links. They control which stage executes next and must evaluate true for the link to be followed.

Debugging with Step and Trace

Process Studio offers Step, Step Out, and Trace to execute stages one at a time. Breakpoints pause execution so data values can be inspected.

Application Modeller

Application Modeller defines an application and its elements (windows, buttons, fields). Objects use these elements to identify and interact with the target application.

Spy modes

Spy modes include Win32, Accessibility, UIAutomation, Region, and HTML. The correct mode depends on the target application's technology and control types.

Match attributes

Match attributes (Window Text, Class Name, Control ID, etc.) identify elements. Combining attributes and using wildcards improves robustness across sessions.

Attach and Detach

Objects attach to an application before interacting and detach when done. Actions that run without an attachment fail because no application context exists.

Wait stage conditions

A Wait stage pauses until a condition is met, such as window exists or element exists. It prevents timing exceptions when applications respond slowly.

Read and Write stages

Read stages extract text or attributes from elements. Write stages set values into elements. Both require a correctly modelled element and an active attachment.

Global Send Keys

Global Send Keys sends keyboard input to the active application. Global Send Key Events sends special keys (Tab, Enter) using encoded syntax.

Atomic Actions

An Action should perform one logical interaction and return meaningful outputs. Atomic Actions are easier to reuse, test, and maintain across Processes.

System vs Business Exception

A System Exception is unrecoverable and terminates the Session. A Business Exception is recoverable and handled by process logic, often marking a queue item exceptioned.

Exception stage

The Exception stage raises an exception with a Type (System or Business), an Exception Type name, and a descriptive Message for logging and diagnosis.

Recover link purpose

The Recover link on a Block stage catches exceptions raised inside the block. It runs cleanup logic and can re-raise or continue execution.

Preserving exception detail

When re-raising an exception, preserve the original Exception Type and Message so the root cause is retained for logging and diagnosis.

Cleanup in Recover path

The Recover path should close applications, release locks, and reset state before re-raising. This prevents orphaned resources and inconsistent state.

Queue item states

Work Queue items move through New, In Progress, Completed, Exceptioned, and Deferred states. Deferred items return to New after the deferral period.

Get Next Item locking

Get Next Item locks an item to the requesting Session. The lock is released on completion, exception, or timeout, allowing other Sessions to process it.

Unique item keys

Each queue item needs a unique key. Adding items with duplicate keys is rejected, which prevents duplicate processing across Sessions.

Queue attempts and deferral

Maximum Attempts limits retries for failed items. Deferral sets how long an item waits before returning to New for another attempt.

Schedules in Control Room

Schedules define when Sessions start. They reference a published Process or Object and a Resource, and can repeat on a defined interval.

PDD and SDD

The Process Definition Document captures the business process. The Solution Design Document translates it into technical design, including Objects, data, and exceptions.

ROM phases

The Robotic Operating Model phases include Process Definition, Solution Design, Solution Configuration, Solution Testing, Solution Deployment, and Post-Implementation.

Configuration separation

Environment-specific values such as URLs, credentials, and file paths belong in Environment Variables, not hard-coded in Processes or Objects.

Testing levels

Test at unit (Object), integration (Process), and user acceptance levels. Use representative test data and verify queue outcomes and exception paths.

Deployment via release packages

Publish Objects and Processes, export them as release packages, import into the target environment, and verify Environment Variables before starting Sessions.

Logging and auditability

Log key events and exceptions with meaningful messages. Blue Prism's session logs and queue audit trails support troubleshooting and compliance review.