Blue Prism AD01 Practice Test - Questions Answers, Page 9

Blue Prism Visual Business Objects (VBOs) are pre-built automation components that need to be imported into the environment. These VBOs are stored in the Blue Prism installation directory.

**[Root Directory]\Program Files\Blue Prism Limited\Blue Prism Automate\VBO**: This is the correct directory where the VBOs can be found. It contains the necessary VBO files that can be imported into Blue Prism.

Other options do not accurately represent the location of the VBOs:

Option A: Incorrect path format.

Option B: Refers to a training directory, which is not the standard location for VBOs.

Option D: Too general and does not specify the correct sub-directory for VBOs.

Reference Refer to Blue Prism installation documentation for the location of Visual Business Objects.

To retrieve items from a work queue tagged with 'Gas' or 'Electric' and exclude items tagged with 'Dual', you need to use a tag filter that excludes the 'Dual' tag. In Blue Prism, the correct way to exclude items tagged with 'Dual' is to use the '-' operator before the tag name, like -Dual. This ensures that only items tagged with either 'Gas' or 'Electric' but not 'Dual' are retrieved.

The Blue Prism documentation on work queues and tagging explains how to use the '-' operator to exclude specific tags.

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.

Blue Prism Process Design guidelines

Data type conversion functions in Blue Prism

In Blue Prism, there are specific stages that are available in Object Studio but not in Process Studio. These stages are designed to interact with applications and perform specific actions at a more granular level.

Option A (Action Stage): Found in Object Studio. It allows the object to call actions within other objects or business objects.

Option B (Read Stage): Found in Object Studio. It is used to read data from an application or interface.

Option E (Write Stage): Found in Object Studio. It is used to write data to an application or interface.

These stages are part of the functionality provided by Object Studio for interacting directly with applications, and they are not available in Process Studio, which is used for high-level process orchestration.

Blue Prism Object Studio documentation

Blue Prism Process Studio documentation

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.

Blue Prism Developer Documentation: Best Practices for Wait Stages

Blue Prism Training Material on Intelligent Wait Stages

Analysis of the Launch Action:

The action involves launching an order processing application, which brings up a login screen requesting the user's login details.

The flow in the question shows a 'Launch' stage and an 'End' stage with no intermediate stages.

Blue Prism Best Practices:

According to Blue Prism best practices, after launching an application, it is essential to verify that the application has loaded successfully and is ready for further interaction.

This verification is typically done using a wait stage to check for the presence of specific elements that confirm the application is ready, in this case, elements on the login screen.

Reasoning for the Wait Stage:

The Wait stage ensures that the login screen has fully loaded and the elements are available for interaction.

This prevents the automation process from proceeding to the next steps too quickly, which could lead to errors if the elements are not yet ready.

Implementation:

Insert a Wait stage immediately after the Launch stage.

Configure the Wait stage to check for a specific element on the login screen, such as the 'Staff Number' field or the 'Sign In' button.

Only proceed to the next stages (entering login details, etc.) once the Wait stage confirms the presence of the required elements.

Blue Prism Developer Documentation: Best Practices for Wait Stages

Blue Prism Training Material on Login Automation Procedures

Understanding Blue Prism Stages:

Blue Prism automation involves various stages that represent different actions and decisions in a process or object. These stages are used to build process flows in both Process Studio and Object Studio.

Certain stages are common to both studios, while some are specific to one.

Identification of Stages in the Image:

Option A: Decision Stage

Option B: Calculation Stage

Option C: Multi-Calculation Stage (a combination of calculations)

Option D: Data Item

Option E: Process Stage

Option F: Navigate Stage (specific to Object Studio)

Stages Common to Both Process Studio and Object Studio:

Decision Stage (Option A): Used to make decisions based on conditions.

Calculation Stage (Option B): Used to perform calculations.

Multi-Calculation Stage (Option C): Represents multiple calculations grouped together.

Data Item (Option D): Represents variables or data items used in the process.

Process Stage (Option E): Used to invoke sub-processes or other processes within a main process.

Stage Specific to Object Studio:

Navigate Stage (Option F): Used to interact with applications, specific to Object Studio.

Blue Prism Developer Documentation: Process and Object Studio Stages

Blue Prism Training Material on Building Processes and Objects

Analysis of the Requirement:

The task is to ensure that the 'New Order' screen in the Centrex Data Solutions application is in focus before Blue Prism interacts with it.

Ensuring the screen is in focus means making it the active window so that subsequent automation actions, such as clicking or entering text, can be performed correctly.

Available Configurations:

Option A: Uses the 'Unhide Window' action.

Option B: Uses the 'Activate Application' action.

Option C: Uses the 'Click Window Centre' action.

Option D: Uses the 'Focus' action.

Evaluation of Each Option:

Option A (Unhide Window): This action would unhide the window if it were hidden, but it does not necessarily bring the window into focus.

Option B (Activate Application): This action ensures the application is active, but it might not specifically bring the 'New Order' window into focus.

Option C (Click Window Centre): This action clicks in the center of the 'New Order' window, which effectively brings it into focus by simulating a user click. This is a direct way to ensure the window is in focus.

Option D (Focus): This action would set focus to the element, but in the provided screenshots, this configuration does not seem to be utilized or shown.

Conclusion:

Option C (Click Window Centre) is the correct configuration because it directly interacts with the 'New Order' window to ensure it is in focus by clicking on its center. This action guarantees that the window becomes the active window, ready for further automation steps.

Blue Prism Developer Documentation: Interacting with Application Windows

Blue Prism Training Material on Window and Element Interaction

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.

Blue Prism Developer Documentation: Using Navigate Stages

Blue Prism Training Material on Application Interaction