A screen contains four buttons, Find, Save, Close and New. When the buttons are spied, the attributes are identical except for the Window Text attribute.
The values for the Windows Text attribute are Find' for the Find button. 'Save' for the Save button, Close' for the Close button and New' for the New
Button.
The Dynamic Button element has been spied and has the following attributes set:
What additional configuration is required to ensure the Close button is selected by the Navigate stage?
Answer : B
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.
Which of the following statements about spy modes are TRUE?
Answer : D
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.
Reference Refer to Blue Prism's documentation on spy modes, which explains the appropriate use cases for each mode.
Refer to the exhibit.
A Filename is the path and file name to which the Excel file should be saved Which of the following Expressions would return a valid Filename?
Answer : D
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' '')&' xhx' (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.
Reference Refer to Blue Prism's documentation on string manipulation and expression building to understand how to correctly concatenate strings to form file paths.
Please refer to the exhibit.
The Developer is automating an SAP Windows-based application within a Citrix environment. There is an issue with a duplicate match found when identifying and highlighting the Document No. field, due to the application window having two of the same labels and buttons.
Which Spy Mode should the Developer use to identify the correct field using Surface Automation?
Answer : D
In a Citrix environment, where traditional spying modes might not work effectively due to the nature of remote desktop applications, Surface Automation techniques are used. The Region mode allows you to define specific areas of the screen to interact with, making it suitable for environments where duplicate elements are present.
Region (Option D): This spy mode allows you to define a specific area on the screen and interact with elements within that region. This is particularly useful in Citrix environments where other spy modes might fail to differentiate between duplicate elements.
The other options are less effective in this scenario:
Win32 (Option A): This mode is used for traditional Windows applications but might not work well in a Citrix environment.
Browser (Option B): This mode is designed for web-based applications and is not suitable for Windows applications in Citrix.
Application Navigator (Option C): This mode is not typically used for surface automation in Citrix environments.
Reference Consult Blue Prism's documentation on surface automation techniques and best practices for automating applications in Citrix environments.
Please refer to the exhibit.
Here's one of the Actions in a Business Object that is used to place orders in an application.
What best practice for Object Design is NOT followed in this Action page?
Answer : D
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.
Please refer to the exhibits
Under what TWO conditions will the process move to the 'Close Down' page directly from the Stop? Decision stage during runtime?
Answer : A, B
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.
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.
A Blue Prism Developer is creating a process that will review travel request forms for ACME consulting. As part of this process, the Developer must ensure that none of the fields in the request are blank.
Following best practice, where should the Developer create this logic"?
Answer : B
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.
Reference Refer to Blue Prism's best practices documentation on process design, which emphasizes modularity and separation of concerns.