Blue Prism AD01 - Blue Prism Accredited Developer Exam

Analyzing the Exhibit:

The exhibit shows a flow with a Wait stage, a Timeout stage, and a Recover stage.

A Recover stage is used to handle exceptions by marking the start of exception handling.

Identifying the Issue:

Option A: The Recover stage should not be an Alert stage. Recover stages are correctly used for exception handling.

Option B: Correct. A Resume stage is missing after the Recover stage. After handling an exception with a Recover stage, a Resume stage is necessary to continue the process flow.

Option C: It is correct to link to a Recover stage to handle exceptions.

Option D: Conditions for the Wait stage are not relevant to the issue with the Object design shown in the exhibit.

Conclusion:

The incorrect aspect of the Object design is B. A Resume Stage is missing.

References:

Blue Prism Developer Documentation: Exception Handling and Recovery

Blue Prism Training Material on Exception Management

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.

References:

Blue Prism documentation on exception handling and recovery stages.

Reason: As we need to pass the values in the username so the values of username to be passed only in the username element. As Rest other options are having only the outer area of the spied application.

This expression will evaluate to true as long as the number of attempts is less than the maximum number of attempts, which means the process will try again. If the expression is false, it means the number of attempts has reached or exceeded the maximum number of attempts, which means the process will throw an exception. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

Understanding the Global Send Key Events Action:

The 'Global Send Key Events' action is used to send keystrokes to a Windows application, simulating keyboard input.

Stage Types in Blue Prism:

Keypress Stage: This does not exist as a separate stage in Blue Prism.

Navigate Stage: This stage is used for performing navigation actions within an application, including mouse clicks, key presses, and global send key events.

Action Stage: This is used to call actions from business objects, not for direct interaction like sending key events.

Write Stage: This is used to enter data into fields, not for sending key events.

Conclusion:

The correct type of stage used to perform a 'Global Send Key Events' action in Blue Prism is the Navigate Stage.

References:

Blue Prism Developer Documentation: Using Navigate Stages

Blue Prism Training Material on Application Interaction

Tagging Exception Items:

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging:

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits:

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.

References:

Blue Prism documentation on exception handling, tagging, and logging.