AD01 Questions and Answers

• 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 the Diagram and Process Flow:
• Exception Handling in Blue Prism:
• Recover Stage Focus:
• Conclusion:

References:

• Blue Prism Developer Documentation: Exception Handling and Recovery Stages
• Blue Prism Training Material on Debugging and Exception Management

• 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: Only the choice stage is found in both process and object studio rest all other stages are found only in the object studio.

Reason: This is because when we are running the process in testing and development phase at time the speed of running the process is slow, that’s why it ran properly and when we haven’t give the proper wait stage and when the process ran in control room the exception occurs as the process ran in full speed so the process is not having the time to wait.

This is mentioned in the Process creation exercise or Lifecycle exercise.

In Blue Prism, collection columns are referenced in expressions using dot notation. This allows for dynamic and precise access to specific data within a collection.

• Expressions (Option B): When you need to reference a specific column in a collection within an expression, you use dot notation. For example, if you have a collection named EmployeeData with a column named FirstName, you would reference it as EmployeeData.FirstName in an expression.

The other options are not correct in this context:

• Loop Properties (Option A): While loops interact with collections, they do not use dot notation to reference columns.
• Work Queue (Option C): Work queues handle items as a whole and do not use dot notation for columns within collections.
• Business Object (Option D): While Business Objects can manipulate collections, the specific reference to collection columns using dot notation is primarily used in expressions.

ReferencesConsult Blue Prism's documentation on expressions and how to work with collections within them for precise data referencing using dot notation.

Spy modes in Blue Prism are used to interact with different types of applications. The correct statements about spy modes are:

• Browser Mode is the default mode used for web-based applications (Option D): This is the most accurate statement. Browser Mode is specifically designed for interacting with web-based applications and is the default mode for such cases.

The other options are incorrect:

• Accessibility Mode is the most commonly used for open source web applications (Option A): Accessibility Mode is used for interacting with applications designed with accessibility in mind, not necessarily open source web applications.
• Win32 Mode is the default mode used for web-based applications (Option B): Win32 Mode is used for desktop applications that use the Win32 API, not web-based applications.
• HTML Mode is the most commonly used when a Code Stage is required (Option C): HTML Mode is used for web applications, but the use of a Code Stage does not determine the spy mode.

ReferencesRefer to Blue Prism's documentation on spy modes, which explains the appropriate use cases for each mode.

• Exception Handling Logic:
• Issue in Logic:
• Resulting Infinite Loop:

References:

• Blue Prism documentation on proper use of exception functions and recovery stages.

• 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

• Analysis of the Requirement:
• Available Configurations:
• Evaluation of Each Option:
• Conclusion:

References:

• Blue Prism Developer Documentation: Interacting with Application Windows
• Blue Prism Training Material on Window and Element Interaction

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

References:

• Blue Prism documentation on loop stages and decision stages.

• Delivery Lifecycle Phases:
• Missing Phase:

References:

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

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.

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.

• Reset Action in Business Object:
• Launch Action:
• Application Window:

References:

• Blue Prism documentation on debugging and Business Object behavior during resets.

• Understanding the Global Send Key Events Action:
• Stage Types in Blue Prism:
• Conclusion:

References:

• Blue Prism Developer Documentation: Using Navigate Stages
• Blue Prism Training Material on Application Interaction

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.

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)

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

• Data Item Exposure:
• Environment Variables:
• Implementation:

References:

• Blue Prism documentation on Data Item exposure and Environment Variables.

• Data Items:
• Calculation Expression:

"Recent Activity for "& [Data3]& " -" &

" Orders: " & [Data1] &

" Refunds: " & [Data2]

• Breaking Down the Expression:
• Combining the Results:
• Final Output:

References:

• Blue Prism documentation on data item manipulation and string concatenation.

Following best practices for Blue Prism development, it is essential to keep validation logic separate from the core business process to enhance maintainability and clarity. This approach ensures that validation is modular and can be easily updated or reused.

• Process Studio, a separate page within the process containing validation logic (Option B): This is the best practice for implementing validation logic. By creating a separate page within the Process Studio, the validation logic remains organized and distinct from other parts of the process. This approach allows for easy updates and debugging.

The other options are less ideal for the following reasons:

• Object Studio a business object dedicated to validating the form (Option A): While this is a valid approach, it is generally better to keep validation within the process logic rather than creating a separate object solely for validation.
• Process Studio: an action on the main page calling a Business Object's Validation page (Option C): This complicates the process unnecessarily by involving an additional business object.
• Object Studio a separate page within the create request object containing validation logic (Option D): Keeping validation within the Object Studio ties it too closely to the specific object, making it less flexible and reusable.

ReferencesRefer to Blue Prism's best practices documentation on process design, which emphasizes modularity and separation of concerns.

Feel free to ask if you have any more questions or need further assistance!

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

Below is the reference.

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.

• 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

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.

• 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

• Understanding Blue Prism Stages:
• Identification of Stages in the Image:
• Stages Common to Both Process Studio and Object Studio:
• Stage Specific to Object Studio:

References:

• Blue Prism Developer Documentation: Process and Object Studio Stages
• Blue Prism Training Material on Building Processes and Objects

• Understanding Priorities:
• Setting Priorities:
• Implementation:

References:

• Blue Prism documentation on work queue priorities.

• Importing Release Files:
• Handling Conflicts:

References:

• Blue Prism documentation on importing release files and handling conflicts.

In Blue Prism, specific stages are unique to either Process Studio or Object Studio. The Option A stage is known as the "Anchor Stage," which is only found in Process Studio. It is used to create flowchart diagrams by connecting various stages, helping to visualize the process flow.

The other options represent stages that can be found in Object Studio or both studios but not exclusive to Process Studio:

• Option B: This is the "Wait Stage," which can be found in both Process and Object Studio.
• Option C: This is the "Navigate Stage," commonly used in Object Studio.
• Option D: This is the "Decision Stage," which can be found in both Process and Object Studio.

ReferencesConsult Blue Prism documentation that outlines the stages available in Process Studio and their specific use cases.

• 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

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.