Understanding the Scenario:

The developer is unable to make changes to the elements in the Application Modeller.

This could be due to several reasons including permissions, application state, or system configurations.

Possible Reasons for Inability to Edit:

Option A: If the shared application model is locked for edits, it prevents any changes from being made until it is unlocked.

Option B: If the user account does not have the necessary permissions, they will be unable to make changes to the application model.

Option C: The run mode of the object being set to Exclusive would affect execution but not the ability to edit in Application Modeller.

Option D: The target application not being launched or attached would affect element spying but not the ability to edit existing elements.

Option E: If Application Modeller is opened during process runtime, it could limit some functionalities but should not generally prevent editing.

Conclusion:

The two reasons that prevent the developer from making changes to the elements in the Application Modeller are:

A. Shared Application Model is locked for edits.

B. User account does not have the permissions.

References:

Blue Prism Developer Documentation: Application Modeller Permissions

Blue Prism Training Material on Shared Application Models and User Permissions

Reason: It updates the values immediately.

Exception Handling :

When an error occurs and is captured by the Recovery stage, it is often necessary to re-throw the same exception after attempting any retry logic.

Preserve Exception Details :

The option to " Preserve the type and detail of the current exception " ensures that the original exception details are not lost and can be propagated further.

This is crucial for accurate logging and troubleshooting, as it keeps the original context of the exception.

Configuration :

In the Exception stage properties, tick the " Preserve the type and detail of the current exception " checkbox.

Leave other fields such as " Exception Type " and " Exception Detail " to their defaults, as these are unnecessary when preserving the existing exception details.

References :

Blue Prism documentation on exception handling and recovery stages.

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

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

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

Environment Lock :

Environment Locks are used in Blue Prism to ensure that only one Digital Worker can access a shared resource, such as an Excel file, at a time.

Implementation :

By implementing an Environment Lock, the process will prevent multiple Digital Workers from accessing and updating the Excel file simultaneously. This ensures data integrity and prevents conflicts.

Correct Approach :

This is the best practice for controlling access to shared resources in a multi-worker environment.

References :

Blue Prism documentation on Environment Locks and their usage.

Operational Handbook :

An operational handbook provides detailed instructions and information on how to operate and maintain a Blue Prism process. It includes information on handling common issues, process flows, and roles and responsibilities.

Benefits :

A. Ensure business continuity : Provides clear guidelines to keep the process running smoothly even when team members change.

B. Faster resolution of issues : Contains troubleshooting steps and solutions for common problems.

D. Knowledge transfer : Helps in training new team members and transferring knowledge efficiently.

Not a Benefit :

C. Real-time analytics : The operational handbook is not intended to provide real-time analytics. This is typically achieved through monitoring tools and dashboards.

References :

Blue Prism documentation on operational handbooks and their benefits.

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.