Pass the Blue Prism Developer AD01 Questions and answers with ExamsMirror

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.

References:

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

In Blue Prism, to construct a valid file path from a root folder and a file name, you need to concatenate these two strings with the appropriate directory separator (backslash in Windows). The correct expression combines the root folder, a backslash, and the file name to form a complete path.

[Root Folder]&''&[File Name] (Option D): This expression correctly concatenates the root folder and the file name with a backslash in between, forming a valid path. For example, if [Root Folder] is "C:\Users\Exam Taker\Downloads" and [File Name] is "File_to_Save.xlsx", the result would be "C:\Users\Exam Taker\Downloads\File_to_Save.xlsx".

The other options are incorrect:

ReplacedFile Name]," xlsx" "")&" xh»x" (Option A): This contains syntax errors and incorrect handling of file extensions.

[Root Folder)&[File Name]&'\xlsx" (Option B): This incorrectly places the file extension as a separate string, and there is a syntax issue with the parenthesis.

LoadTextFile([Root Folder]&''&" xisx" (Option C): This uses an incorrect function (LoadTextFile) and has a typo in the extension.

ReferencesRefer to Blue Prism's documentation on string manipulation and expression building to understand how to correctly concatenate strings to form file paths.

Startup Parameters:

Startup parameters allow a process to be configured with specific input data before it runs. This can be used to customize the behavior of the process based on the provided inputs.

Setting Startup Parameters:

In Control Room, you can set startup parameters by right-clicking the session for the process you want to run and selecting "Startup Parameters".

This allows you to input the necessary data directly before the process starts, ensuring it runs with the correct configuration.

References:

Blue Prism documentation on setting and using startup parameters.

To ensure that only credit transactions are included when calculating the total of customer credits, the 'Credit Transaction?' decision stage needs to check if the transaction code is between 50 and 99. Given that transaction codes are stored as text, we need to convert these values to numbers before performing the comparison.

Customer Transactions Collection:

The 'Transaction Code' column contains text values representing the transaction codes.

Credit Transaction Identification:

Credit transactions have transaction codes between 50 and 99.

Therefore, the correct condition should convert the text transaction code to a number and check if it is greater than or equal to 50.

Decision Stage Expression:

The correct expression is ToNumber([Customer Transactions.Transaction Code]) >= 50, which ensures that only credit transactions are included in the total calculation.

References:

Blue Prism Process Design guidelines

Data type conversion functions in Blue Prism

Importing Release Files:

When importing a Blue Prism release file, the system checks for conflicts with existing objects or VBOs in the environment.

Handling Conflicts:

If there is already a Business Object or VBO with the same name in the environment, the user is prompted to either rename the new object or overwrite the existing one.

This ensures that the user can manage potential conflicts and maintain control over which version of the object is active in the environment.

References:

Blue Prism documentation on importing release files and handling conflicts.

Spy Mode:

Blue Prism uses different spy modes (e.g., Win32, HTML, Region, etc.) to interact with various types of applications and elements within those applications.

Testing in Process Studio vs. Control Room:

A process may work in Process Studio because elements are correctly identified during testing, but it may fail in Control Room if the wrong spy mode was used, leading to elements not being found in the live environment.

First Check:

Verify that the correct spy mode was used to identify the screen elements. This ensures that the process can reliably locate and interact with these elements during runtime.

References:

Blue Prism documentation on spy modes and element identification.

Understanding the Exception:

The error message indicates that the read stage 'Read Nasdaq Data' failed because it was not connected.

This suggests that the business object might not be correctly attached to the application or not launched.

Analyzing Possible Causes:

Option A: Internal errors do not always indicate a Blue Prism product problem; they can also result from configuration issues.

Option B: If the action was not published, the error would likely indicate that the action could not be found, not an attachment issue.

Option D: If the action no longer existed, the process would not be able to call it, and the error would reflect that the action was missing.

Option E: The process flow shows the stages are connected, and an unconnected stage would not specifically cause an attachment error.

Most Likely Cause:

Option C is the most likely reason. If the business object is not associated with the application (either by launching or attaching to it), the action cannot be performed because Blue Prism does not have the necessary context to interact with the application.

References:

Blue Prism Developer Documentation: Exception Handling and Troubleshooting

Blue Prism Training Material on Application Modelling and Object Association

Understanding Work Queue Icons in Blue Prism:

Each work queue icon in Blue Prism represents a different status of a work queue item.

Icons and Their Meanings:

Option A (Checkmark): This indicates that the item has been completed successfully.

Option B (Flag): This icon typically represents an item that is waiting to be worked on or is flagged for attention.

Option C (Lock): This indicates that the item is locked and cannot be processed.

Option D (Three Dots): This icon represents a case that is currently being worked on by a digital worker.

Conclusion:

The icon that indicates a case is waiting to be worked is Option B (flag).

References:

Blue Prism Developer Documentation: Work Queue Icons and Status Indicators

Blue Prism Training Material on Work Queue Management

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.

References:

Blue Prism documentation on Data Item exposure and Environment Variables.

In Blue Prism, a Clean Up page is used to perform finalization tasks as the business object is closed down. This can include tasks such as closing all instances of applications, saving any final state, and releasing resources. The Clean Up page is called automatically by Blue Prism when the business object is disposed of at the end of a business process.

Option A (Close All Instances): This is the correct use of the Clean Up page. It involves closing all instances of the application or resources that were used during the process. This ensures that no instances are left open, which could otherwise lead to resource leaks or conflicts.

The other options are not ideal for the Clean Up page:

Option B (Save Workbook): While saving a workbook might be necessary, it is more appropriate to do this as part of the main process or just before the clean-up if it is part of the final steps in the business process.

Option C (Save Workbook): Similar to Option B, this does not fit the primary use case for a Clean Up page.

Option D (Exit): While exiting might seem appropriate, it is too generic and does not convey the specific actions needed for cleaning up resources.

ReferencesRefer to Blue Prism's best practices and documentation on using Clean Up pages to ensure that resources are properly finalized and released at the end of a business process.