In Blue Prism, an expression is a statement that is evaluated at runtime to produce a value. It is essentially a formula constructed from data items, literals, operators, and built-in functions. Expressions are fundamental components used within various stages, most notably the Calculation stage to compute a result and the Decision stage to evaluate a condition to either True or False, thereby directing the process flow. The expression itself is the logic or formula, not the resulting output or descriptive text.

B. An output from a Decision stage is a control flow path (e.g., 'True' or 'False'), which is determined by the evaluation of an expression, but it is not the expression itself.

C. The description of a Blue Prism stage is a text field used for documentation and annotation; it is not a formula and is not executed by the process.

D. The output from a Calculation stage is the value produced by the expression, which is then stored in a data item. The expression is the formula used to generate that output.

1. Blue Prism Official Documentation Portal: Data Types and Expressions Guide. In the "Expressions" section

it is stated: "An expression is a statement that can be evaluated to produce a value. Expressions are made up of data

contained in data items

and literals

which are manipulated by operators and functions." This directly supports that an expression is a formula used to produce a value.

2. Blue Prism Official Documentation Portal: v7 User Guide - Process Studio. In the section "Calculation Stage

" the guide describes the 'Expression' field as the area where the user enters "the expression to be evaluated." The 'Store Result In' field is separately defined for the output value

distinguishing the expression from its result.

3. Blue Prism Official Documentation Portal: v7 User Guide - Process Studio. The "Decision Stage" section explains that the stage "evaluates an expression" to determine which of two paths to follow. This reinforces that the expression is the evaluative logic

not the resulting path.

In Blue Prism's Application Modeller, the Ordinal attribute is the primary tool used to resolve "duplicate match" errors. When multiple elements share identical attributes (like Class Name, Name, or Type), the Ordinal attribute allows the Application Manager to identify an element based on its position in the search order (e.g., the 1st, 2nd, or 3rd instance found). By enabling Ordinal and assigning a specific integer value, you instruct the robot to select one specific instance among the duplicates, ensuring a unique match.

A. Child Count: This identifies how many children an element has; while it can differentiate containers, it rarely provides a unique identifier for standard input fields like passwords.

B. Parent Class Name: This identifies the class of the parent container. If multiple identical fields exist within the same window structure, the Parent Class Name will likely be identical for all.

C. Parent Ordinal: This distinguishes between multiple parent elements. While useful if the parents are duplicates, it does not directly resolve the duplication of the specific child element (the password field) itself.

E. Class Name: The Class Name is often generic for input fields (e.g., "Edit" or "TextBox"). Since the error already states multiple matches were found, the Class Name is clearly not unique.

Blue Prism University: Introduction to Object Design - Application Modeller Section (Version 6.0+), "Working with Attributes and Identification."

Blue Prism Official Documentation: Guide to the Application Modeller, Section: "Attribute Selection," Subsection: "Using Ordinal and Match Index to resolve duplicates."

Blue Prism Academic Support: Foundation Training Guide, Chapter 5: "Object Studio," Topic: "Spying Elements and Handling Duplicate Matches."

In Blue Prism, each stage has a distinct visual identifier:

1. Note Stage: A simple white rectangle used for annotations.
2. Multi Calc: Distinguished by the "Stage" tab at the top-left, allowing multiple calculations in one step.
3. Process Stage: Represented by double vertical bars, indicating a call to a sub-process.
4. Block Stage: Identified by dashed lines; it is used for exception handling to group stages.
5. Action Stage: Depicted as stacked hexagons, used to call Business Objects and their respective actions.

Blue Prism University: Foundation Training - Process Studio (Edition 6.0 and above), Section: "Process Flow and Stages Overview."

Blue Prism Help Guide: Reference -> Process Studio Stages, specifically the "Note Stage," "Calculation and Multi-Calculation," and "Action Stage" documentation.

Blue Prism User Guide: Exception Handling and Blocks, Chapter 7: "The Block Stage."

Blue Prism Online Documentation: Design Best Practices - Visual Indicators, Section: "Sub-processes and Action Calls" (v6.x/v7.x).

The ExceptionType() function is the dedicated internal function in Blue Prism used to retrieve the classification of the current exception (e.g., "Business Exception", "Internal Exception", or "System Exception"). When an exception is caught by a Recover stage, this function becomes active and can be utilized within a Calculation stage to populate a data item. While ExceptionDetail() captures the specific error message text, ExceptionType() specifically extracts the category or "type" of the error, which is exactly what the "Save Exception Type" stage in your diagram is designed to do.

Blue Prism Official Documentation: v6.10/v7.1 Help Guide, "Exception Functions" section, specifically defining ExceptionType() as returning the type of the current exception as a text value.

Blue Prism University: Foundation Training Course, Module 7: "Exception Management," detailing the use of calculation stages to store exception metadata.

Blue Prism Professional Developer Certification (APD01) Syllabus: Section on "Advanced Exception Handling," identifying the scope and application of ExceptionType(), ExceptionDetail(), and ExceptionStage() functions.

Blue Prism Design Best Practices: Standard Exception Handling Template, Page 8, "Data Collection during Recovery," reinforcing the use of ExceptionType() for logging purposes.

A Blue Prism Process is the primary mechanism for implementing automation. It is created in Process Studio using a flowchart-like interface. This graphical representation is not just a diagram but a fully functional, executable program. Its purpose is to define a logical sequence of steps that a Digital Worker (robot) follows to interact with various applications and data sources, thereby automating tasks that are typically manual, repetitive, and rules-based. This definition correctly combines its visual nature, its executable functionality, and its core purpose within Robotic Process Automation (RPA).

A. A business flow diagram: This is an incomplete description. While a Process looks like a flow diagram, it is an executable program, not just a static visual representation.

B. A computer application: This term is too broad. A Process is a specific type of program that operates within the Blue Prism runtime environment, not a standalone application like Microsoft Word.

C. A business flow chart: Similar to option A, this only describes the visual aspect of a Process and omits its crucial nature as a working, executable program.

1. Blue Prism Ltd. (2020). Blue Prism Foundation Training - Introduction to Blue Prism. In the section "What is a Blue Prism Process?"

it is stated: "A Blue Prism Process is a diagram that looks like a common business flow diagram. The diagrams are graphical representations of a working computer program... The program is used to automate tasks that are performed by users of IT systems." (Paraphrased from conceptual descriptions in early training modules).

2. Blue Prism Ltd. (2021). Blue Prism - Process Studio (v7.0). The guide's introductory sections describe a process as the object where the logic for an automated task is defined. It emphasizes that the flowchart created in Process Studio is the "logic of the automation

" which is then interpreted and executed by a runtime resource. This confirms it is more than a simple diagram. (See Section: "Process Studio Overview").

In Blue Prism, "Exception Bubbling" is the official term for the mechanism where an unhandled exception propagates up the call stack. If an exception occurs on a sub-page and is not caught by a Recover stage on that same page, it "bubbles up" to the calling page. This process continues until the exception is handled by a Recover stage or until it reaches the Main Page. If an exception bubbles all the way to the Main Page and remains unhandled, the process will terminate. This behavior allows for centralized exception handling strategies on higher-level pages.

A. Exception Queuing: This is not a standard Blue Prism term for exception propagation. It might refer to placing failed items into a work queue, which is a different concept.

B. Exception Deferral: This term is not used in Blue Prism. It implies postponing exception handling, not the immediate upward propagation described.

D. Exception Resolution: This refers to the outcome of handling an exception (i.e., fixing the issue), not the process of how an unhandled exception travels through the process hierarchy.

1. Blue Prism Corporation. (2021). Data Sheet - Exception Handling. "If an exception is not caught on the page on which it occurs

it ‘bubbles up’ to the page that called the current page. This allows exceptions to be handled centrally." (Section: Exception Bubbling

Paragraph 1).

2. Blue Prism University. (2022). ASDEV01: Blue Prism Certified Associate Developer Courseware. "Module 6: Exception Handling". The module explicitly describes the concept of an exception "bubbling up" from a sub-page to a parent page if not handled locally

which is a core principle tested for the ASDEV01 certification.

In Blue Prism, the 'Flag' data type is specifically designed to store boolean values. It can only hold one of two states: True or False. This data type is the direct equivalent of a boolean variable in other programming languages and is the most appropriate and efficient choice for managing binary logical conditions within a process or object. Using a Flag data item allows for direct use in logical expressions and decision stages without the need for type conversion or string/number comparison.

A. Binary: This data type is used for storing raw binary data, such as the contents of a file or an image, not a simple logical True/False value.

B. Number: While a number (e.g., 1 or 0) could be used to represent True/False, it is not the dedicated data type and requires interpretation, making it less clear and efficient.

C. Text: This data type stores character strings. Storing "True" or "False" as text is inefficient and requires string comparisons rather than direct boolean logic.

E. Password: This is a specialized, secure data type for storing sensitive information like credentials. It is not used for storing boolean values.

1. Blue Prism Official Documentation: "Data Types". In the Blue Prism interactive help and online documentation

the 'Flag' data type is explicitly defined. It states

"A flag data item can be either True or False." This is the fundamental definition provided within the product's own guide. (Accessed via Blue Prism Portal > Documentation > Product Guides for any recent version

e.g.

v7.0

under the "Data Types" section).

2. Blue Prism Foundation Training (ASDEV01 syllabus): "Module 3: Process Studio". This foundational training module introduces Data Items and their various types. It specifies that the 'Flag' data type should be used for any data that represents a True/False or Yes/No condition.

3. Blue Prism - Data Types (v6.10 Guide): Page 4

"Data Types Table". The table lists all available data types. For 'Flag'

the description is "A value which can be either True or False." This official guide directly confirms the purpose of the Flag data type.

The Decision stage is the fundamental component in Blue Prism for controlling process flow based on a condition. It evaluates a logical expression that results in a True or False outcome. In this scenario, after calculating the customer's age (likely in a preceding Calculation stage), a Decision stage would be used to test the condition [Age] < 18. Based on the True/False result, the process is directed down one of two distinct paths, allowing it to handle underage customers differently from adults, thereby fulfilling the requirement.

A. Calculation stage: This stage is used to perform data manipulation and calculations, such as finding the age from a date of birth, but it cannot conditionally alter the process flow.

B. Business Rule stage: This is not a standard, distinct stage type in the Blue Prism Process Studio palette. Business rules are implemented using stages like Decision.

C. Validation stage: This is not a standard, distinct stage type in Blue Prism. Data validation is a concept implemented using a combination of stages, primarily Decision and Exception stages.

---

1. Blue Prism Corporation. (2023). Blue Prism Process Studio v7.2 User Guide.

Section: "Decision Stage"

Content: The guide explicitly states

"A Decision stage is used to ask a question

the answer to which determines the path taken by the process... The expression entered must be one that evaluates to either True or False." This directly supports its use for testing the customer's age against a threshold.

2. Blue Prism University. (2022). Foundation Training - Process Flow.

Module: "Decisions"

Content: The training material describes the Decision stage as the primary mechanism for creating branches in a process. It emphasizes that a decision diamond always has two outgoing paths (True/False)

which is precisely what is needed to separate customers based on an age check.

3. Blue Prism Corporation. (2023). Data Sheet: Blue Prism Process Studio.

Section: "Core Components"

Content: The data sheet lists and describes the main stages available. It defines the Decision stage for conditional logic and branching

while the Calculation stage is defined for executing expressions and assigning results to data items. It does not list "Business Rule" or "Validation" as stage types.

The Queues area within the Blue Prism Control Room serves as a central management interface for Work Queues. It allows authorized users to monitor the overall status and health of queues, including counts of pending, completed, and exception items. Beyond monitoring, it provides critical administrative capabilities for manual intervention. Users can directly change the status of an item to 'Complete' or 'Exception', unlock an item that may be stuck due to a process failure, and manage an item's processing schedule by setting or altering its 'Deferral Date'. These actions are essential for managing workflow, handling errors, and maintaining operational continuity.

D. Lock a Work Queue item: Locking is an automatic mechanism performed by a running process when it retrieves an item using the 'Get Next Item' action; it cannot be initiated manually by a user in Control Room.

1. Blue Prism - User Guide: Control Room (v7.0)

Section: Queue Management

Page 12. This section details the actions available from the context menu for a selected work queue item. It explicitly lists "Set Status" (which includes Complete and Exception)

"Unlock Item"

and "Set Deferral Date" as available manual actions. The main view inherently provides the ability to review the queue status.

2. Blue Prism - Work Queues Guide (v6)

Section: Working a Queue

Page 11

Paragraph 2. This guide explains the locking mechanism: "When a case is retrieved from the queue using the Get Next Item action

the case is locked by Blue Prism so that other resources which are working the queue cannot retrieve the same case." This confirms locking is a programmatic action

not a manual Control Room function.

3. Blue Prism Online Help Portal (v7.2)

Topic: Queue Management. The documentation for the Queue Management page in Control Room describes the user interface and available actions. It states

"You can perform a number of actions on queue items

such as retrying exception items

setting the status of items

and deleting items." It further details the context menu options

which include unlocking and setting deferral dates.

Blue Prism's Credential Manager is the designated and secure repository for storing sensitive information, such as usernames and passwords. It encrypts the credentials within the Blue Prism database and provides robust, role-based access control. This ensures that only authorized processes and users can access and utilize the credentials, and their usage is fully audited. Storing credentials in this centralized, secure manner is a fundamental security best practice for Blue Prism development, preventing exposure of sensitive data within process logic or external files.

A. In a local hidden file: This method is insecure as hidden files are easily discoverable and offer no encryption or access control, exposing credentials.

B. In a password protected file: This is not a recommended practice as it lacks the granular access control, robust encryption, and audit capabilities of Credential Manager.

D. Environment Variable: Environment Variables are intended for non-sensitive configuration data, not for credentials, as they are not encrypted and are broadly visible in System Manager.

E. In Data Items in the Process: Storing credentials in Data Items is a major security risk, as they would be visible in plain text to anyone viewing the process.

F. In a shared Excel file: This is highly insecure and unmanageable, lacking proper encryption, access controls, and auditing required for sensitive credential data.

1. Blue Prism - Product Help v7.2

"Credentials" section: "The Blue Prism Credential Manager provides a secure

centralized repository for storing credentials... Credentials stored in the Blue Prism database are encrypted using a combination of symmetric and asymmetric encryption." This document explicitly defines Credential Manager as the secure location for credentials.

2. Blue Prism - Data Sheet: Secure & Compliant Credential Management

Page 1: "Blue Prism’s Credential Manager provides the capability to securely store and manage credentials that are used by Digital Workers when interacting with target applications." This source confirms the purpose-built nature of Credential Manager for this exact scenario.

3. Blue Prism - Credential Management (v6)

Section 1.1

"Introduction": "The Blue Prism Credential Manager provides the facility to securely store credentials that are used by Blue Prism processes when interacting with target applications. The credentials are encrypted and stored in the Blue Prism database and can only be retrieved by processes that have been granted the appropriate permissions." This directly supports the use of Credential Manager over all other options.