Blue Prism 6.10.3: October 2021

Database

468

This release requires the Blue Prism database to be this version.

Login agent

6.10.3

There have been no functional updates to the Blue Prism Login Agent. The version of Login Agent that is provided with this release of Blue Prism has the same functionality as the version provided with Blue Prism 6.7.

Browser extensions
(for Chrome, Firefox,
and Edge):

6.10.3

For the latest compatibility information, see the browser compatibility matrix in the Blue Prism online help.

Authentication Gateway

1.0

Authentication Gateway version 1.0 must be installed to use Authentication Gateway with Blue Prism 6.10.3.

Download the installer from the Blue Prism Portal – select Product > Blue Prism Enterprise > Extras.

Data Gateways engine

1.3

The Data Gateways engine version 1.3 must be installed to use Data Gateways with Blue Prism 6.10.3.

Download the installer from the Blue Prism Portal – select Product > Blue Prism Enterprise > Extras.

Known issues

A list of any prominent issues with this release is maintained in the knowledge base – click here for more information.

Important notices

Please review the upgrade notices for more details and before upgrading to this release.

Enhancements

Description of change

Reference

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.

BP-5623

(BP-5099)

BP-5734 (BP-5518)

The Edge browser extension is now fully installed if selected on the Advanced install screen during Blue Prism installation. Previously, it was necessary to enable the extension separately in the Edge browser once the Blue Prism installation had completed.

BP-5493

From Blue Prism 6.8 onwards, the default communication between browser extensions and Blue Prism is via a dynamically selected port from the ephemeral range. The system setting Use fixed browser extension port (31924) only allows administrators to override the default behavior when using older versions of the browser extensions which communicate with Blue Prism via a fixed port.

Blue Prism 6.10.3 includes the following changes to improve the robustness of Chrome, Edge, and Firefox browser automations and provide a more seamless upgrade path:

Deployment scenario Use fixed browser extension port (31924) only system setting
New Blue Prism installation Selected by default – Connection via fixed port
Upgrading from Blue Prism versions earlier than 6.8 Selected by default – Connection via fixed port

Upgrading from Blue Prism version 6.8 and later

If the setting has been manually set (irrespective of its value), then the setting will be retained.

If the setting has not been manually set, it will be unselected by default in System Settings and the browser connection will be via an ephemeral port.

System administrators can still select/deselect the system setting Use fixed browser extension port (31924) only as required to change the port connection.

BP-5492

Fixes and minor improvements

Description of change

Reference

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.

BP-5214

BP-4912

BP-6376

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.

BP-5765

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.

BP-5575

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.

BP-310

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.

BP-5658

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.

BP-6053

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.

BP-6046

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.

BP-5596

BP-5697 (BP-4501)

BP-5700 (BP-5291)

To reduce unnecessary memory usage while running automations, once received from the application server, runtime resources now store a single instance of the compressed process and object XML. Previously, such XML files were stored uncompressed and any previously retrieved versions since the last restart were retained, which caused runtime resources to run out of memory when running large, complex processes.

BP-5698 (BP-4420)

Browser extension versions

The table below shows when each Blue Prism extension, compatible with this release was introduced. For details of the latest browser versions Blue Prism is tested against, see the Browser extension compatibility matrix.

Browser Blue Prism extension versions Date available

Chrome

6.10.3

19 October 2021

Edge Chromium

6.10.3

19 October 2021

Firefox

6.10.3

19 October 2021