Master the Blue Prism AD01 Exam: Essential Study Tips and Strategies

The golden rules for Object Design in Blue Prism focus on creating modular, reusable, and maintainable objects. These rules are:

• Keep actions small and limited to a specific task (Option A): This ensures that actions are simple, easy to understand, and reusable.
• Do not include business logic in the Object (Option B): Business logic should be handled in the Process layer, keeping objects focused on interacting with applications.
• Use Input/Output parameters to promote usability (Option C): This enhances the flexibility and reusability of objects by allowing different data to be passed in and out of actions.

However, using a single Object for an entire application (Option D) is not recommended. This approach would result in a monolithic and difficult-to-maintain object. Instead, it is better to create multiple objects, each handling a specific part of the application or a specific type of interaction.

ReferencesRefer to Blue Prism's best practices and guidelines on Object Design, which emphasize modularity, separation of concerns, and reusability.

In Blue Prism, certain stages can be found in both Object Studio and Process Studio. These stages are:

• Read Stage (Option C): This stage is used to read data from elements and variables. It is available in both Object Studio and Process Studio.
• Write Stage (Option D): This stage is used to write data to elements and variables. It is also available in both Object Studio and Process Studio.

The other stages listed in the options are specific to either Object Studio or Process Studio, but not both.

ReferencesRefer to the Blue Prism documentation and training materials which outline the stages available in Object Studio and Process Studio.

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."

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

• Loop Structure:
• Condition:
• Loop Execution:
• Outcome:
• Final Report:

References:

• Blue Prism documentation on loop stages and decision stages.

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.

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

The process will move to the 'Close Down' page directly from the 'Stop?' Decision stage under two conditions:

• The specified Stop time has passed: This condition checks if the current local time exceeds the configured stop time. In the provided Decision Properties, the condition LocalTime() > [Stop After Time] evaluates if the current time is beyond the stop time.
• 'Request Stop' received from Control Room: This condition is checked by the IsStopRequested() function. If the Control Room sends a stop request, this function returns true, causing the process to move to the 'Close Down' page.

Other conditions like Stop After Items and an immediate stop request from the Control Room are not mentioned in the process depicted in the exhibits. Therefore, only the two conditions mentioned above apply.

References:

• The Decision stage properties and conditions as shown in the provided exhibit.
• Blue Prism documentation on Decision stages and Control Room interactions for stopping processes.

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.

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