Blue Prism AD01 Exam Questions

Pausing a Schedule:

Pausing the schedule is the best practice for temporarily stopping a process. This maintains the schedule's configuration and simply suspends its execution for the specified period.

Maintaining Configuration:

Pausing the schedule ensures that once the period is over, the same schedule can be resumed without needing to recreate it or adjust any start/end dates. This approach is simpler and minimizes the risk of configuration errors.

Reactivation:

After the required period, the schedule can be easily unpaused to resume its normal operation.

Blue Prism documentation on scheduling and best practices for managing schedules.

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.

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.

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

Delivery Lifecycle Phases:

The typical phases in the delivery lifecycle of an RPA project include Define, Design, Build, Test, UAT (User Acceptance Testing), and Deploy.

Missing Phase:

The phase between Define and Build is Design. This phase involves creating detailed designs of the automation, including process flows, system interfaces, and data requirements.

Blue Prism delivery lifecycle documentation and project management best practices.

Reset Action in Business Object:

When debugging an action page within a Business Object, clicking the Reset button will reset the focus to the Start stage of the current page.

Launch Action:

If the current action page includes stages that interact with an application, the focus will typically return to the Start stage of the Launch action, ensuring that the application is in the correct state for the next steps.

Application Window:

Resetting the action page does not automatically close the application window unless explicitly programmed to do so within the actions.

Blue Prism documentation on debugging and Business Object behavior during resets.