Blue Prism 7.1.2: December 2022

An issue has been fixed where Domain Controller name mappings configured manually for an Active Directory domain, as described here, were not being loaded into Blue Prism when validating credentials whilst adding or editing domain credentials. This issue prevented users of Active Directory environments that require Domain Controller Name mappings to be set for a domain (for example, environments using an Active Directory multi-site infrastructure) from logging into Blue Prism using Active Directory authentication.

In previous 7.1 versions, if an existing Active Directory (AD) user in Blue Prism was deleted from Active Directory prior to upgrading a single-authentication AD database to version 7.1, and a new user was added after the upgrade who had the same User Principal Name (UPN) as the deleted user, the deleted user account was incorrectly reactivated and updated with the unique security identifier (SID) of the new AD user once the AD user list was synchronized with Blue Prism.

This was because the system could not find the SID of the deleted user in Active Directory and thus searched using the UPN, which would lead to the incorrect matching behavior. This behavior has now been updated so if a user is not found in Active Directory based on the SID, it will be automatically deleted in the Blue Prism database, and no longer searched for via the UPN.

Active Directory users with the same User Principal Name (UPN) as an existing or deleted user can now be added if their security identifier (SID) is different.

An error no longer occurs when synchronizing Active Directory users in Blue Prism and one or more users’ Distinguished Name (DN) is null.

An error caused by a case sensitivity difference between the configured Active Directory domain name preference and the Active Directory domain record in the database no longer occurs when an Active Directory user is attempting to log into the Blue Prism interactive client using a direct database connection.

Active Directory users can be synchronized and log into Blue Prism using telnet commands and web service requests when their UPN contains an alias suffix that is different to the Domain Name System (DNS) name of the Active Directory domain. For example, corp.dir.company.com (DNS name) and company.com (alias suffix), where [email protected] is the UPN. Blue Prism will automatically determine available alias suffixes for the users unless configured manually by an administrator. An optional database script to configure alias suffixes is available for download from the Blue Prism Portal.

Several performance improvements have been made when determining Active Directory group membership for a user during authentication, and when viewing the roles assigned to a user in Blue Prism. For more information, see Single sign-on troubleshooting.

When executing a process against a 64-bit Java application, an error triggering the message Arithmetic operation resulted in an overflow no longer occurs when automating data in Java tables using the Get All Items action. This has been fixed by updating the conversion mechanism so long values are converted to integer values.

The following issues have been fixed when working with application elements that are using a Match Index attribute with a value greater than 0:

• The Java changes introduced in version 6.10.3 by BP-5374 and in version 7.0.1 by BP-6163 no longer cause intermittent crashes of Java applications that were automated using the Java Access Bridge spy mode.
• The Get Element Bounds actions in Read Stages, which dynamically read values from a Java application, no longer incorrectly return negative values instead of positive values.

An error no longer occurs when clicking the Test Connection button on the Connection Configuration after upgrading to Blue Prism 7.1 and using an existing database name. The error only occurred when using the Create Database option to replace the old database, but not when using the Upgrade Database option.

The message that displays when an error occurs whilst attempting to access AutomateC commands has been made more informative.

An issue has been fixed where, following an upgrade to Blue Prism 7.1 from 6.10 or earlier, existing processes, business objects, and actions were not available or resulted in errors if any Description fields included a brace (curly bracket).

Imported web services now display in the Business Object drop-down in the Action Properties dialog in Process and Object Studio. Previously, the BPAWebServiceAsset table was not populated after importing a web service.

A new System - Timeouts section in System Manager displays timeout parameters used in Blue Prism automations. These can be changed if the default configuration is causing issues in a particular environment, and to optimize automations across environments. Any changes should only be made under guidance from Blue Prism and tested in a development environment. For more information on the parameters and their functions, see Timeout parameters.

An issue has been fixed where a web page that was being spied using a Chrome or Edge browser extension could not be highlighted or spied again once a file had been downloaded from the web page. The Chrome or Edge browser extension no longer disconnects from Blue Prism once a download has been triggered.

The way the browser type is detected by the native messaging host has been updated to remove the reliance on performance counters, as corrupt or disabled performance counters would prevent the native messaging host from launching correctly.

Blue Prism can now successfully terminate browser applications when the external 32-bit or 64-bit Application Manager mode is used. Previously, an error occurred when attempting to terminate a browser application which had been attached using an external application model.

Previously in Blue Prism versions 7.0.1 to 7.1.1, an error occurred when attempting to attach to a Chrome, Edge, or Firefox browser page using only the process ID (PID) without specifying a title for the page. This has now been fixed by removing the check for the window title when a PID is provided.

The 32-bit version of Blue Prism Enterprise now includes the 32-bit version of the native messaging host. Previously, the 64-bit version of the native messaging host was incorrectly installed.

The Parent Document Loaded action, used in a Wait stage when automating a Chrome, Edge, or Firefox browser, now checks whether the parent document was loaded. Previously, it was incorrectly set to always return a true value.

System timeout parameters used in browser automations can now be configured in the Chrome, Edge, and Firefox browser extension settings to allow system administrators to optimize automations on a particular machine.

Blue Prism now remains attached to a web page even if the window title changes. Previously, when the window title of a browser instance changed, the browser extension could not be detected and an error message displayed.

When attempting to attach to a browser for which the provided window title is incorrect, a message indicating the specific error now displays immediately. Previously, Blue Prism would wait for 60 seconds before displaying a general message that the browser extension could not be detected.