Blue Prism AD01 Practice Test - Questions Answers, Page 11

The provided diagram represents an Action page in a Business Object that is used to place orders. According to best practices for Object Design in Blue Prism, actions should primarily focus on interacting with the application rather than containing business rules or decision-making logic. The following points explain why Option D is the correct answer:

Avoid applying business rules and decision-making logic in an Action (Option D): Business rules and decision-making should be handled in Process Studio, not in Object Studio. The decision regarding 'Quantity Under Limit?' in the diagram is a business rule and should be part of the process logic, not the object logic.

Other options are essential best practices but are not violated here:

Use a conditional Wait stage to confirm the screen change (Option A): This is followed as the diagram shows a Wait stage confirming the screen change.

The timeout of the Wait stage should lead to a System Exception (Option B): This is followed as the diagram shows a system exception being thrown upon a timeout.

An action page should first confirm if the application is connected (Option C): This is followed as the action begins by checking the connection to the 'New Order Window.'

Reference Refer to Blue Prism's best practices for Object Design, which emphasize separating process logic and object interaction logic.

In Blue Prism, the Wait stage is used to pause the process until specific conditions are met or a timeout occurs. The following points explain why Option B is the correct answer:

If all conditions are met before the TimeOut period expires, the process will continue (Option B): This is the correct behavior of the Wait stage. If the specified conditions are met before the timeout period, the process will continue without waiting for the entire timeout duration.

The other options are incorrect:

The Wait Stage will sequentially check each condition, it does not require all conditions to be met (Option A): This is incorrect because the Wait stage does not check conditions sequentially but rather waits for any specified condition to be met.

If no conditions are met, an internal error will appear and terminate the process (Option C): This is incorrect; if no conditions are met within the timeout period, the process will follow the timeout path, which may or may not terminate the process depending on how it is handled.

The Wait Stage will simultaneously check all conditions and follow the logic of whichever condition is met first (Option D): This is incorrect because the Wait stage waits for any one of the conditions to be met before the timeout, rather than following the logic of the first met condition.

Reference Refer to Blue Prism's documentation on the Wait stage and its behavior in processes, highlighting how conditions and timeouts are managed.

In Blue Prism's Application Modeller, the 'Identify' button offers different options for identifying and working with elements in an application. Understanding the difference between the 'Spy Element' and 'Navigator' options is crucial for effective element identification and automation design.

Spy Element (Option D): This option allows you to manually identify an element to use in the Application Modeller. When you select 'Spy Element,' you manually click on the element within the application to capture its attributes and use them for automation.

Navigator Options (Option D): The Navigator options, including 'Open Application Navigator' and 'Open UI Automation Navigator,' display a tree of elements available to choose from. These navigators allow you to browse through a hierarchical view of elements in the application, making it easier to select and identify elements that might be difficult to manually spy.

The other options are incorrect because:

Option A: This does not accurately describe the functionality of the Spy Element and Navigator options.

Option B: This option misrepresents the primary use of the Navigator options, which is for browsing and selecting elements rather than debugging.

Option C: This is the reverse of the actual functionality. The Spy Element is used for manual identification, while the Navigator options display a tree of elements.

Reference Consult Blue Prism's documentation and user guides on Application Modeller and element identification methods to understand the distinct functionalities of Spy Element and Navigator options.

To ensure Blue Prism best practices are followed in respect to naming conventions and layout, the developer should design the object with the following action pages: Launch, Attach, Login, Navigate, and Terminate. Each of these action pages serves a distinct purpose, making the object modular and easier to maintain.

Launch: This action page is used to start the application.

Attach: This action page is used to attach to the running instance of the application.

Login: This action page is used to handle the login process.

Navigate: This action page is used to navigate through different menus or pages within the application.

Terminate: This action page is used to close the application properly.

Option C follows these best practices by including Launch, Attach, Login, Navigate, and Terminate action pages, ensuring the object is well-structured and adheres to naming conventions.

The other options do not fully comply with these best practices:

Option A: Does not include a Terminate action page, which is important for cleanly closing the application.

Option B: Uses 'Orders' instead of a more generic 'Navigate' and does not include Terminate.

Option D: Similar to Option C but uses 'Centrix Data Solutions - Basic Actions' instead of the more specific naming convention 'Basic Actions -- Centrix 01.'

Reference Refer to Blue Prism's best practices documentation on Object Design, emphasizing modularity, clear naming conventions, and distinct action pages for different functionalities.

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.