AD01 Sample Questions Answers

• Analysis of the Launch Action:
• Blue Prism Best Practices:
• Reasoning for the Wait Stage:
• Implementation:

References:

• Blue Prism Developer Documentation: Best Practices for Wait Stages
• Blue Prism Training Material on Login Automation Procedures

• Understanding the Breakpoint:
• Analyzing the Breakpoint Condition:
• Possible Outcomes:
• Conclusion:

References:

• Blue Prism Developer Documentation: Debugging and Breakpoints
• Blue Prism Training Material on Conditional Breakpoints

Reason: This is happening when identifying the elements in application modeler some of the details which are changing on the different environment and while identifying the elements in application modeler the developer takes the element whose values are changing and when the application run on the different path at that point of the time the process is able to expecting values eg same url, date or title but it is not at there so the process terminates. Follow the best practice for this.

• Defined within the Object Layer:
• Actions Built to No Specific Hierarchy:
• Incorrect Options:

References:

• Blue Prism documentation on the Object layer and Business Objects.

• Understanding Blue Prism Flow Representations:
• Analysis of Options:
• Conclusion:

References:

• Blue Prism Developer Documentation: Exception Handling
• Blue Prism Training Material on Process Flow and Error Management

Reason: When passing the values in the Parameter the parameter should be configured with respect to the window text and pass as the value “close” as other attributes are identical we only have window text to make our fingerprint unique.

• Understanding the Scenario:
• Possible Reasons for Inability to Edit:
• Conclusion:

References:

• Blue Prism Developer Documentation: Application Modeller Permissions
• Blue Prism Training Material on Shared Application Models and User Permissions

Reason: As we need to pass the values in the username so the values of username to be passed only in the username element. As Rest other options are having only the outer area of the spied application.

• Stage Logging in Production:
• Decision Stage:
• Best Practice:

References:

• Blue Prism best practices for logging and monitoring in production environments.

Reason: Session variable values to be update only in the Control room.

Below is the reference.

Reason: This is happening when the application is not attached or launched and user tries to read the action. Exercise also mentioned in the foundation course. Below snapshot is from the Exception pdf.

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.

References:

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

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.

The Saved Quantity data item will contain the sum of all the Quantity values in the Orders collection after the loop. The loop will iterate through each row of the collection and add the value of Quantity to the Saved Quantity data item using a calculation stage. The initial value of Saved Quantity is 0, and after adding each row’s Quantity, it will become 19 (0 + 4 + 5 + 1 + 9). References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

When encountering an error due to multiple similar elements on a web page with the same name, it's crucial to use an attribute that ensures a unique match.

• Match Index (Option D): This attribute is specifically designed to handle situations where multiple elements have similar properties. By setting the Match Index, you can specify which instance of the element should be used, ensuring a unique match.

The other options are less effective in this scenario:

• Web Text (Option A): This may not be unique if multiple elements have the same text.
• Ordinal (Option B): While it indicates the order, it’s less precise compared to Match Index.
• Web Element Type (Option C): This doesn't help in distinguishing between multiple similar elements.

ReferencesConsult Blue Prism's best practices for dealing with web automation and handling multiple similar elements on a page. The Match Index attribute is commonly recommended for these cases.

To resolve the error at the Navigate stage when using a dynamic input value to navigate the left menu links in a web-based application, it is crucial to ensure the Web Target Address attribute is set correctly.

• 'Web Target Address' attribute should be checked for the element (Option A): This attribute helps Blue Prism identify the correct target address for navigation. Ensuring it is checked and properly configured will allow Blue Prism to navigate accurately.

Other options may not address the root cause effectively:

• 'Web Path/X Path' attribute should have '= (Equal)' as the Match Type (Option B): This is not necessary if the dynamic value is already used effectively.
• 'Value' field of the Web Text attribute should be cleared (Option C): Clearing the value may result in the element not being found at all.
• 'Web Page Address' attribute should be unchecked for the element (Option D): This could cause navigation issues if the page address is not correctly identified.

ReferencesRefer to Blue Prism's documentation and best practices for configuring web elements and attributes for navigation stages.

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

Reason: A) when spying the application, blueprism fetch all the elements of the target application only, blue prism doesn’t provide any elements of its own.

C) Attributes are vary from application type to type. Attributes are different for windows, browsers, mainframe, java.

D) Reason is below.

• Spy Mode:
• Testing in Process Studio vs. Control Room:
• First Check:

References:

• Blue Prism documentation on spy modes and element identification.

• Revisiting the Issue:
• Analyzing the Possible Reasons:
• Conclusion:

References:

• Blue Prism Developer Documentation: Collections and Global Data Items
• Blue Prism Training Material on Data Item Scope and Visibility

Intelligent wait stage should always be used after every stage and that should be minute wait to overcome the lag when the application runs and on wait should only be used when some of action interfacing the screens or any updating is going on as per the best practices pdf

Reason: Is is common as the duplicate elements we are found by default as the attributes are provided by the application not by the blue prism. how do make our elements unique is not done by practicing and experience. ( This is also mentioned in the Foundation course and as well as in other Pdf too)

In Blue Prism, to construct a valid file path from a root folder and a file name, you need to concatenate these two strings with the appropriate directory separator (backslash in Windows). The correct expression combines the root folder, a backslash, and the file name to form a complete path.

• [Root Folder]&''&[File Name] (Option D): This expression correctly concatenates the root folder and the file name with a backslash in between, forming a valid path. For example, if [Root Folder] is "C:\Users\Exam Taker\Downloads" and [File Name] is "File_to_Save.xlsx", the result would be "C:\Users\Exam Taker\Downloads\File_to_Save.xlsx".

The other options are incorrect:

• ReplacedFile Name]," xlsx" "")&" xh»x" (Option A): This contains syntax errors and incorrect handling of file extensions.
• [Root Folder)&[File Name]&'\xlsx" (Option B): This incorrectly places the file extension as a separate string, and there is a syntax issue with the parenthesis.
• LoadTextFile([Root Folder]&''&" xisx" (Option C): This uses an incorrect function (LoadTextFile) and has a typo in the extension.

ReferencesRefer to Blue Prism's documentation on string manipulation and expression building to understand how to correctly concatenate strings to form file paths.

• Understanding Input Parameters and Collections:
• Possible Reasons for Collection Not Being Visible:
• Conclusion:

References:

• Blue Prism Developer Documentation: Collections and Global Data Items
• Blue Prism Training Material on Data Item Scope and Visibility

• Understanding the Process Flow:
• Calculation Stage Expression:
• Analysis of Options:
• Conclusion:

References:

• Blue Prism Developer Documentation: Calculation Stages
• Blue Prism Training Material on Data Item References

• Delivery Lifecycle Phases:
• Missing Phase:

References:

• Blue Prism delivery lifecycle documentation and project management best practices.

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

References:

• Blue Prism documentation on loop stages and decision stages.

Using environment variables is a best practice in Blue Prism for managing configuration settings that may vary across different environments (e.g., Testing, Development, Training, and Production). This approach allows for easy updates and changes without modifying the underlying code.

• Environment Variable: Storing the URLs in an environment variable allows you to change the URL for different environments without altering the business object or process code. This makes the automation more flexible and easier to maintain.

Other options are less optimal:

• Build per URL (Option A): Creating separate objects for each URL is inefficient and increases maintenance effort.
• Dynamic Match (Option B): This does not specifically address URL management.
• Global Data Items (Option C): While global data items can store URLs, environment variables are more suited for managing environment-specific configurations.

ReferencesRefer to Blue Prism's best practices on managing environment-specific configurations using environment variables.

Loop Orders is configuring to the Orders collection and as per the diagram in the order collection there are 15 rows so the loop is run till 15 times and the process order page will executed 15 times.

A sub-page in a process can have only one start stage, which is where the execution begins when the sub-page is called from another page. A sub-page cannot have zero or more than one start stages, as that would cause ambiguity or confusion in the execution flow. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

• Understanding the Calculation Stage:
• Analyzing the DateAdd Function:
• Interval Values in DateAdd Function:
• Conclusion:

References:

• Blue Prism Developer Documentation: Date Functions
• Blue Prism Training Material on Calculation Stages and Date Manipulation

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.

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