Blue Prism AD01 - Blue Prism Accredited Developer Exam

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.

References:

Blue Prism documentation on Release Manager and package management.

When working with the Blue Prism Application Modeller, the visibility of an element is critical for ensuring that it can be consistently interacted with by Blue Prism. The "Screen Visible" attribute determines whether the element is currently visible on the screen. However, this attribute can sometimes cause issues if the element is off-screen or hidden but still needs to be interacted with by Blue Prism.

Screen Visible (Option B): Unticking this attribute ensures that Blue Prism can interact with the element even when it is not visible on the screen. This helps in maintaining consistent visibility and interaction with the element regardless of its on-screen status.

The other attributes are important for identifying and interacting with the element:

Window Text (Option A): This attribute is necessary to identify the text within the window.

Visible (Option C): This indicates whether the element is visible; unticking this might cause inconsistency.

Class Name (Option D): This attribute helps identify the type of UI element, crucial for correct interaction.

ReferencesBlue Prism's best practices for application modelling and attribute selection emphasize maintaining consistency and reliability in element interaction by carefully managing visibility attributes.

Reason: As the business object is only configure in the Object studio.

Rest all other reasons are failed.

Initial Analysis of the Action Flow:

The Action flow starts with writing the Customer ID, followed by clicking the search button, reading the results table, counting the result rows, and ending the flow.

This flow represents an automation process in Blue Prism, interacting with a user interface or application.

Importance of Wait Stages:

Wait stages in Blue Prism are used to handle the timing issues when interacting with applications. They ensure that the application has had enough time to process the previous action before moving to the next.

Without wait stages, the automation process might attempt to perform actions on elements that are not yet ready, leading to errors.

Identification of Critical Points for Wait Stages:

After the start stage and before interacting with the application elements, it is important to introduce wait stages to ensure the application is ready.

Specifically, after the 'Write Customer ID' stage and after the 'Click Search Button' stage, wait stages should be added because these actions cause changes in the application state, which needs to be stabilized before proceeding.

Implementation:

Add a wait stage after the 'Start' stage to ensure the application is loaded and ready.

Add another wait stage after 'Write Customer ID' to ensure the ID is fully entered before clicking the search button.

Another wait stage should be placed after 'Click Search Button' to wait for the results to load before reading the results table.

After reading the results table, ensure the table is fully loaded before counting the result rows.

References:

Blue Prism Developer Documentation: Best Practices for Wait Stages

Blue Prism Training Material on Intelligent Wait Stages

Reason: Global send key events and global keys are not passed through the navigate stage.

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.

Reason: collection name or data type should always pass in square braces. And if you want to pass any column from the collection than use it as a dot notation after the collection name in the same braces. (You can check this in foundation course or by doing practically)