Single Object Design :

According to Blue Prism best practices, it is generally recommended to minimize the number of objects and actions to keep the solution simple and maintainable.

Actions :

Get Account Details : This action retrieves account information from the screen.

Apply New Limit : This action applies a new limit to the account.

Decision-Making Logic :

The decision-making logic (checking for high-risk code) should be placed in the process, not the object. This separation ensures that the object focuses on interacting with the application, while the process handles the business logic.

References :

Blue Prism best practices on object design and separation of concerns between objects and processes.

Best Practices for Production Release :

A. Disable unnecessary stage logging : This is a best practice to reduce data storage and improve performance.

C. Alerting Mechanism : Including an alerting mechanism helps notify Process Controllers of critical issues, which is crucial for maintaining process health and quick issue resolution.

D. Zero Validation Errors : Ensuring there are no validation errors before deployment helps avoid runtime failures.

Handling Business Exceptions :

Using retry loops to handle business exceptions for work queue items is not recommended as it can lead to unnecessary retries and may not address the underlying issue causing the exception. Instead, business excep tions should be handled by sending them to an exception queue for further analysis and resolution.

References :

Blue Prism documentation on best practices for process development and deployment.

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.

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

The ' Multi1 ' calculation stage in the process flow attempts to perform multiple calculations sequentially. Here are the calculations and the issues they cause:

Initial Values:

Start Value : 10

End Value : 0

Calculations:

[Start Value] * 10 stored in End Value :

10 * 10 = 100

Now, End Value is 100.

5 / [End Value] stored in Start Value :

5 / 100 = 0.05

Now, Start Value is 0.05.

[End Value] + 10 stored in End Value :

100 + 10 = 110

Now, End Value is 110.

However, if these calculations were performed strictly in the order they appear in the table, the initial End Value of 0 would cause a division by zero error on the second calculation ( 5 / [End Value] ), resulting in an internal exception before any values could be reassigned. Therefore, the correct answer is that an internal exception for division by zero will be thrown.

References:

Blue Prism Process Design guidelines

Error handling documentation in Blue Prism

Understanding the Process Diagram:

The diagram includes a calculation stage named " Get Date of Previous Day " and a data item named " Result Date " .

The Calculation Properties window shows the expression Yesterday() used in the calculation stage.

Analysis of the Calculation Stage:

The Yesterday() function is used to get the date of the previous day.

The result of this function is stored in the " Result Date " data item.

Data Type Considerations:

Option A: This option is incorrect because there are correct statements regarding the process diagram.

Option B: If " Result Date " is configured as a Text data type, a ' data type mismatch ' Internal Exception will indeed be thrown because the Yesterday() function returns a date, not text.

Option C: If " Result Date " is configured as a Date data type, the Yesterday() function will correctly set " Result Date " to the previous day ' s date.

Option D: This option is incorrect because the Yesterday() function is valid and will not throw a ' Failed to evaluate expression ' Internal Exception if used correctly with a date data type.

Conclusion:

The correct statement is:

C. If the ' Result Date ' data item is configured as a Date data type, then the ' Result Date ' data item will be set to the date of the previous day on execution of the Calculation stage.

References:

Blue Prism Developer Documentation: Date Functions

Blue Prism Training Material on Calculation Stages and Date Manipulation