Understanding the Requirements:

The developer needs to perform the following actions using the Navigate stage:

Bring the application screen to the foreground.

Send a ' Global Mouse Click Centre ' command to the center of the Username field.

Use Global Send Keys to populate the Username field.

Steps to Achieve the Requirements:

Bring the application to the foreground: This can be done using the ' Activate Application ' action on the ' Login Window ' .

Send a ' Global Mouse Click Centre ' command: This can be done by selecting the ' Global Mouse Click Centre ' action on the ' Username ' element.

Use Global Send Keys to populate the Username field: This can be done by selecting the ' Global Send Keys ' action on the ' Username ' element.

Analyzing the Options:

Option A:

Launch action on the ' Login Window ' : Correct for bringing the application to the foreground but not suitable for already running applications.

Click Window Centre on ' Login Window ' : Not the best approach for focusing on a specific element.

Global Send Keys on ' Username ' : Correct for sending keys but requires prior focus on the Username field.

Option B:

Activate Application on the ' Login Window ' : Correct for bringing the application to the foreground.

Global Mouse Click Centre on ' Username ' : Correct for clicking the center of the Username field.

Global Send Keys on ' Username ' : Correct for sending keys to the Username field.

Option C:

Activate Application on the ' Login Window ' : Correct for bringing the application to the foreground.

Global Mouse Click Centre on ' Username ' : Correct for clicking the center of the Username field.

Global Send Keys on ' Username ' : Correct for sending keys to the Username field.

Option D:

Attach action on the ' Login Window ' : Not necessary for bringing the application to the foreground if it is already running.

Global Mouse Click Centre on ' Username ' : Correct for clicking the center of the Username field.

Global Send Keys on ' Username ' : Correct for sending keys to the Username field.

Conclusion:

The correct configuration is Option C because it uses:

' Activate Application ' action to bring the application to the foreground.

' Global Mouse Click Centre ' action to click the center of the Username field.

' Global Send Keys ' action to populate the Username field.

References:

Blue Prism Developer Documentation: Navigate Stage and Actions

Blue Prism Training Material on Spying Modes and Application Interaction

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

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

Exception Handling Best Practices :

Proper exception handling involves not only recovering from an error but also ensuring the system is ready for subsequent operations.

This typically includes resetting the application or any global data to a known good state.

Issue in the Main Page :

In the provided diagram, the flow directly connects the Recover stage to the Resume stage without any intermediate logic.

This is problematic because the system might be left in an inconsistent state after an error.

Required Logic :

Implement logic between the Recover and Resume stages to reset the application or any relevant data.

This ensures that after handling an exception, the system is in a known good state and can continue processing new items reliably.

References :

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

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

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:

The ' Transaction Code ' column contains text values representing the transaction codes.

Credit Transaction Identification:

Credit transactions have transaction codes between 50 and 99.

Therefore, the correct condition should convert the text transaction code to a number and check if it is greater than or equal to 50.

Decision Stage Expression:

The correct expression is ToNumber([Customer Transactions.Transaction Code]) > = 50 , which ensures that only credit transactions are included in the total calculation.

References:

Blue Prism Process Design guidelines

Data type conversion functions 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)