Blue Prism 6.10.3: October 2021

The following performance improvements to spying execution times have been made to the Java automation functionality in Application Modeller:

• The time taken to navigate trees in complex applications with a large number of nodes has been significantly reduced.

• The mechanism used to match Java element types (recognize a specific sequence of characters, tokens, and data) during Java automation has been improved when using Match Index as one of the matching attributes, making the match process much faster.

An intermittent issue resulting in a Browser extension was not detected error that prevented elements from being spied no longer occurs when attempting to launch a Chrome, Edge, or Firefox browser. The error occurred either in Studio or when running an automation, in the following scenarios:

• When a process that uses a browser extension is terminated and another process immediately attempts to open another browser before the socket becomes available.

• When attempting to launch a browser immediately after it has been closed. This has been fixed by automatically trying every 200 milliseconds for up to 2 minutes when terminating the browser. If the browser does not successfully close, an error message warns the user to ensure all browsers with the Blue Prism browser extension installed are closed before continuing.

An issue has been fixed where once a process that used the browser extension via a fixed port had been run in Studio, another process that used the same port failed to run in Control Room, and vice versa – on any runtime resource running locally on the same device.

When using Application Modeller to attach to web pages in a Chrome, Edge, or Firefox browser, users no longer need to manually append a wildcard to window titles of target pages taken from a collection. This functionality is now consistent with the window title parameter in stage properties where the wildcard is automatically inferred.

A fix has been applied to ensure that, when entering data into web components in a Chrome, Edge, or Firefox browser, the necessary underlying input event is triggered and the native value setters are used to ensure the event works as expected. The behavior in the application should now be the same both when the web component is worked by a digital worker or by a human using a keyboard and mouse, even in situations where the developers of the web components have programmatically overridden the event.

When using an ephemeral port for Chrome, Edge, and Firefox browser automation, URLs containing %20 are now displayed and used as expected. Previously , %20 was incorrectly replaced with + when launching the browser.

Closures of browser sessions launched from multiple instances of Blue Prism are now correctly detected by the Blue Prism instance which launched the browser session.

In previous versions of Blue Prism 6.10, when one of browser sessions was closed, the Detach button for that session remained enabled in Application Modeller even after if it was clicked by a user, and the closure of that session was only detected once all browser sessions were closed.

Previously, when attaching to an already running instance of Chrome, Edge, or Firefox using the Application Navigator, elements manually selected by the user in the tree view of the application navigator were not highlighted in the browser page, and the right-hand pane of the application navigator was not populated with the selected element's attributes.

Selected elements are now correctly highlighted in the browser and populated in the application navigator.

To enhance performance, the handling of environment variables has been improved so that only a single shared copy of the data is held in memory on a runtime resource per session. Previously, each sub-process or object within a process retrieved and stored its own copy of the environment variables from the database. This fix also prevents unnecessary repeat queries for environment variables in the database each time a process is executed or an object is called from within a process.

Additionally, the error message that displays when data items reference a deleted environment variable in Studio has been improved to make it more informative to users.