Blue Prism AD01 Practice Test - Questions Answers, Page 18

Understanding Priorities:

In Blue Prism, work queue items with a lower priority value are processed before those with a higher priority value.

Setting Priorities:

To ensure that Business Customer cases are worked first, the priority for these cases should be set to the lowest value.

For Business cases, set the priority to '0'.

For all other cases (Personal and Joint), set the priority to '1'.

Implementation:

While adding items to the work queue, use the Add to Queue action to set the priority.

Ensure Business cases have priority '0' and others have priority '1'.

Blue Prism documentation on work queue priorities.

Active Directory Integration:

With Active Directory Integration, user authentication can be managed through the organization's Active Directory, enabling better user management and security.

Encrypt and Decrypt Work Queue Item Data:

With the Credentials Manager functionality deployed, it is possible to encrypt and decrypt sensitive data within work queue items, enhancing data security.

Functionality Added:

These functionalities enhance security and streamline user management in future automations.

Blue Prism documentation on Credentials Manager and its integration with Active Directory and work queue item encryption.

Data Item Exposure:

Setting the Data Item exposure to 'Environment' allows the value to be consistent across different environments without changing the process.

Environment Variables:

Environment Variables can be used to store the file path, ensuring the correct path is used regardless of the environment (UAT, Production, etc.).

Implementation:

Create an Environment Variable to store the file path.

In the process, set the Data Item to use this Environment Variable.

Blue Prism documentation on Data Item exposure and Environment Variables.

Exception Handling:

When an error occurs and is captured by the Recovery stage, it is often necessary to re-throw the same exception after attempting any retry logic.

Preserve Exception Details:

The option to 'Preserve the type and detail of the current exception' ensures that the original exception details are not lost and can be propagated further.

This is crucial for accurate logging and troubleshooting, as it keeps the original context of the exception.

Configuration:

In the Exception stage properties, tick the 'Preserve the type and detail of the current exception' checkbox.

Leave other fields such as 'Exception Type' and 'Exception Detail' to their defaults, as these are unnecessary when preserving the existing exception details.

Blue Prism documentation on exception handling and recovery stages.

Exception Handling Best Practices:

Proper exception handling involves not only recovering from an error but also ensuring the system is ready for subsequent operations.

This typically includes resetting the application or any global data to a known good state.

Issue in the Main Page:

In the provided diagram, the flow directly connects the Recover stage to the Resume stage without any intermediate logic.

This is problematic because the system might be left in an inconsistent state after an error.

Required Logic:

Implement logic between the Recover and Resume stages to reset the application or any relevant data.

This ensures that after handling an exception, the system is in a known good state and can continue processing new items reliably.

Blue Prism documentation on best practices for exception handling and process design.

Defined within the Object Layer:

Blue Prism Business Objects are defined and created within the Object layer. This is where objects interact with external applications, providing a way to encapsulate the application's functionality into reusable components.

Actions Built to No Specific Hierarchy:

Actions within a Business Object are not required to follow a specific hierarchy. They are built to perform specific tasks or operations and can be executed independently of one another.

Incorrect Options:

B . Will always have a Launch action: Not all Business Objects require a Launch action, as it depends on the nature of the application being automated.

C . Can be used as a stand-alone process: Business Objects cannot be used as stand-alone processes. They are designed to be invoked by processes.

D . Do not share any stages with the Process Studio: Business Objects share many stages with Process Studio, such as calculations, decisions, and data items.

Blue Prism documentation on the Object layer and Business Objects.

Data Items and Types:

Sign Up Date: 04-05-2023 (Date data type)

Current Date: 13-06-2023 (Date data type)

Expiry Date: 04-07-2023 (Date data type)

Status: Text data type

Output: Text data type

Decision Stage:

The decision checks if Current Date > Expiry Date.

13-06-2023 is not greater than 04-07-2023, so the decision evaluates to No.

Calc1 and Calc3 Execution:

Since the decision is No, Calc1 and Calc3 are executed.

Calc1 is not shown, but it must set Status to something other than 'Expired' (possibly 'Active').

Calc3 concatenates Status and Expiry Date to form the final output.

Expected Output:

If Calc1 sets Status to 'Active', Calc3 will produce the output:

Subscription Status = Active; Expiration Date = 04-07-2023

Final Output:

Given the logic and data provided, if Calc1 does not change Status from 'Expired' (it wasn't executed due to decision No path):

Subscription Status = Expired. Expiration Date = 04-07-2023

If the decision path was intended to show Expired status, then:

Subscription Status = Expired; Expiration Date = 04-07-2023.

Blue Prism documentation on decision stages and data type handling in expressions.

Exception Handling Logic:

When using ExceptionType() and ExceptionDetail() functions, they must be used within the context of an active recovery stage. These functions retrieve details about the current exception.

Issue in Logic:

In the provided diagram, the Capture Exception Detail stage is executed as a multiple calculation stage but is not within a recovery block. Using these exception functions outside recovery mode can cause another exception.

Resulting Infinite Loop:

This causes a new exception each time the Capture Exception Detail stage is executed, leading to an infinite loop of exceptions as the process continuously tries to recover from the newly generated exceptions.

Blue Prism documentation on proper use of exception functions and recovery stages.

Defined Package Requirement:

To generate a release, you must first define a package. The package includes all the components (processes, objects, etc.) that will be included in the release.

File Types for Import:

Blue Prism allows importing of two types of files: Release files (.bprelease) and Skill packages (.bpskill). These are the only file types that can be imported via the Release Manager.

Incorrect Statements:

A . Release files cannot be imported by anyone regardless of their user permissions. Importing releases requires specific user permissions.

C . The Modify Package wizard does not update previous components released within your environment; it modifies the package for the current release.

E . The Verify wizard does not test a Package's components for changes since the last release; it ensures all components are included and dependencies are met.

Blue Prism documentation on Release Manager and package management.