AD01 Blue Prism Accredited Developer Exam Questions and Answers

• Understanding Work Queue Icons in Blue Prism:
• Icons and Their Meanings:
• Conclusion:

References:

• Blue Prism Developer Documentation: Work Queue Icons and Status Indicators
• Blue Prism Training Material on Work Queue Management

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)

In Blue Prism, wait stages are crucial to ensure that the application is in the correct state before proceeding with further actions. In this scenario:

• Conditional Wait stage after the Attach page: This ensures that after attaching to the application, the process waits until the necessary elements are present before continuing. This is important because the application may take some time to load or change states.
• Conditional Wait stage after the Navigate stage: This ensures that after navigating, the process waits until the target elements are available. This helps to handle any delays in the application response or page loading times.

By configuring wait stages in this manner, you ensure that the process only proceeds when the application is ready, thereby minimizing the risk of errors due to timing issues.

Other options are less optimal:

• Unconditional Wait stage (Options C and D): These do not provide the necessary checks to confirm the application's state and can lead to unreliable automation.
• Wait stage after the Write stage (Option A): This is less relevant if the critical steps are attaching and navigating, which are the primary steps where timing issues are likely to occur.

ReferencesRefer to Blue Prism's best practices on using wait stages to synchronize process execution with the application state.

• 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

• A: [Attempts]
• B: <
• C: [Max Attempts]

So, the final expression should be: [Attempts] < [Max Attempts]

This will correctly check if the current number of attempts is less than the maximum allowed attempts, enabling the process to retry if necessary.

• 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

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.

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.

• 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 Blue Prism Components:
• Capability to Interact with Business Applications:
• Conclusion:

References:

• Blue Prism Developer Documentation: Object Studio and Business Objects
• Blue Prism Training Material on Application Interaction

• Exception Handling:
• Preserve Exception Details:
• Configuration:

References:

• Blue Prism documentation on exception handling and recovery stages.

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.

References:

• Blue Prism Object Studio documentation
• Blue Prism Process Studio documentation

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.

• Active Directory Integration:
• Encrypt and Decrypt Work Queue Item Data:
• Functionality Added:

References:

• Blue Prism documentation on Credentials Manager and its integration with Active Directory and work queue item encryption.

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

References:

• Blue Prism documentation on spy modes and element identification.

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.

• Operational Handbook:
• Benefits:
• Not a Benefit:

References:

• Blue Prism documentation on operational handbooks and their benefits.

• Environment Lock:
• Implementation:
• Correct Approach:

References:

• Blue Prism documentation on Environment Locks and their usage.

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

References:

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

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)

Environmental variables are those variables that are available to all processes and business objects. So, these variables are used as dynamic variables, to make sure they can be used whenever required across the Blue Prism platform.

• Understanding Session Variables:
• Behavior of Session Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Session Variables
• Blue Prism Training Material on Process Execution and Variable Management

• Exception Handling Best Practices:
• Issue in the Main Page:
• Required Logic:

References:

• Blue Prism documentation on best practices for exception handling and process design.

For window application to ensure the new screen is in focus We need to activate the New screen as not the application

• Excel VBO Workflow:
• Correct Order:

References:

• Blue Prism documentation on Excel VBO and its actions.

• Understanding the Diagram:
• Analyzing the Logic:
• Identifying the Issue:

References:

• Blue Prism Developer Documentation: Exception Handling and Retry Logic
• Blue Prism Training Material on Process Flow and Exception Handling

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:
• Credit Transaction Identification:
• Decision Stage Expression:

References:

• Blue Prism Process Design guidelines
• Data type conversion functions in Blue Prism

• Understanding Environment Variables:
• Updating Environment Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Environment Variables
• Blue Prism Training Material on Variable Management and Configuration

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: As the window text is not unique when the value is changed and bp is able to spied at time a error would come. So there is no use of window text.

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

References:

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

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)

When setting the Window Text attribute for an application in Blue Prism, it's often helpful to use wildcards to ensure the element is consistently matched, even if the window title varies slightly. In this case, using a * at the beginning and end of the value will match any window title that contains the text "Centrix Data Solutions - Please Log In".

• Use a * at the beginning and end of the Value (Option B): This will ensure that any leading or trailing characters in the window title will not prevent a match. For example, *Centrix Data Solutions - Please Log In*.

Other options might not be as effective:

• Change the Match Type to Dynamic (Option A): This is unnecessary if the wildcard approach works.
• Position the ''after Solutions' (Option C): This does not make sense in the context provided.
• Change the Match Type to Wildcard (Option D): This would require more specific adjustments to the value itself.

ReferencesRefer to Blue Prism's documentation on attribute matching and the use of wildcards for ensuring reliable element identification.

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.

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

Upon restarting the Blue Prism Server Service, the scheduler will check for any schedules that should have been executed during the downtime. Based on the system configuration, only the schedules within a defined timeframe will be executed. This is typically set in the ‘Execute missed schedules from the past n minutes’ setting within the scheduler configuration. If a schedule is discovered that should have executed multiple times within the configured period, it will only be executed once. Schedules that fall outside of this defined timeframe will not be executed and may be marked as exceptions depending on the system settings

• Session Variables:
• Updating Session Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Session Variables and Data Items
• Blue Prism Training Material on Control Room Operations

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

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

In Blue Prism, a sub-page in a process can have any number of End stages. This is because sub-pages can be designed to handle various branches and paths, requiring multiple endpoints to conclude different process flows. This flexibility allows for more complex and branched process designs, enabling developers to manage various outcomes and logic paths efficiently.

References:

• Blue Prism Process Design guidelines
• Sub-page design documentation in Blue Prism

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)