Tagging Exception Items :

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging :

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits :

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.

References :

Blue Prism documentation on exception handling, tagging, and logging.

Spy Mode :

Blue Prism uses different spy modes (e.g., Win32, HTML, Region, etc.) to interact with various types of applications and elements within those applications.

Testing in Process Studio vs. Control Room :

A process may work in Process Studio because elements are correctly identified during testing, but it may fail in Control Room if the wrong spy mode was used, leading to elements not being found in the live environment.

First Check :

Verify that the correct spy mode was used to identify the screen elements. This ensures that the process can reliably locate and interact with these elements during runtime.

References :

Blue Prism documentation on spy modes and element identification.

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.

Reason: After resume stage the exception is dead so the Re thrown will not worked.

Understanding Priorities :

In Blue Prism, work queue items with a lower priority value are processed before those with a higher priority value.

Setting Priorities :

To ensure that Business Customer cases are worked first, the priority for these cases should be set to the lowest value.

For Business cases, set the priority to " 0 " .

For all other cases (Personal and Joint), set the priority to " 1 " .

Implementation :

While adding items to the work queue, use the Add to Queue action to set the priority.

Ensure Business cases have priority " 0 " and others have priority " 1 " .

References :

Blue Prism documentation on work queue priorities