Blue Prism 7.1.2: December 2022

Click this icon on the toolbar to view and download the full PDF version of the release notes.

About this release

The tables below summarize the components that relate directly to this Blue Prism Enterprise release.

Core components

The following components are included in the Blue Prism Enterprise installers:



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

Browser extensions
(Chrome, Firefox, and Edge)


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

Additional components

The following components are available with this Blue Prism release, but must be installed separately if they are required in your Blue Prism environment:

Login Agent


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

Data Gateways engine


The Data Gateways engine 1.4 must be installed to use Data Gateways with this version of Blue Prism.

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

Blue Prism API


The Blue Prism API version installed must always be the same as the Blue Prism Enterprise version number to use the API.

Download the installer from the Blue Prism Portal via Product > Blue Prism Enterprise > Blue Prism 7.

Compatible Blue Prism Hub components and plugins

The following components are part of the Blue Prism Hub release, but are required to utilize specific Blue Prism functionality:

Authentication Server

4.6, 4.7

This Blue Prism Enterprise release requires this version of Authentication Server to be able to leverage the related new features included in this release of Blue Prism.

For more information, see the Authentication Server configuration guide.

Control Room plugin

4.6, 4.7

The Control Room plugin must be one of this version to leverage the features in this Blue Prism release. The Control Room plugin is dependent on the Blue Prism API.

For more information, see the Control Room plugin guide.

Applying this patch release

To upgrade to this version, this patch release must be applied to all the following components throughout your Blue Prism environment for it to be operational:

Interactive clients Runtime resources Application servers




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

Known issues

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

Secure development policy

SS&C Blue Prism’s secure development process is a market-leading, embedded security culture, focused on delivering security excellence through four key principles:

  • Education – Providing up-to-date knowledge, information, and training to the development team.
  • Evaluation – Regular reviews of our products using industry standard frameworks and security tools.
  • Elimination – Remove potential threats through the evaluation of standards, compliance, and performance.
  • Evolution – Continued improvement of our security program, ensuring alignment with our product technologies and by reacting effectively to new and emerging threats.

SS&C Blue Prism secure development is based on OWASP ASVS, ISO 27034 and GDPR Article 25 standards and practices. For more information, see SS&C Blue Prism's comprehensive secure development process.

Blue Prism core components

The following enhancements, fixes, and minor improvements have been added to the Blue Prism core functionality in version 7.1.2:

Active Directory integration

Description of change


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, (DNS name) and (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.


The following improvements have been made to the behavior of the cache that stores the discovered Active Directory domains:

  • A message has been added to the Blue Prism login page informing Active Directory users that the data cache is currently being populated.
  • An SQL cache has been added to Blue Prism which contains the data cache that is generated when an Active Directory user first logs into Blue Prism. A new database table dbo.BPACache has been added to support this functionality.
  • The default value for the Maximum cache duration has been updated to 1440 minutes (24 hours). Previously, the default was 30 minutes. This will be updated when users click Update Database on the Connection Configuration screen. For more information, see Single sign-on troubleshooting.
  • When used, a new AutomateC command line parameter /requestactivedirectorycacherefresh will trigger an update of the data stored in the cache that was populated when:
    • A direct connection was established to the database.
    • A Blue Prism application server was started.
    • Active Directory authentication was enabled in System > Security - Sign-on settings.

      For more information, see Command line options.





Application Modeller

Description of change


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.


BP-11882 (BP-11136)

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.

BP-11684 (BP-11128)

BP-11743 (BP-9214)

Previously in Blue Prism versions 6.9 to 7.1.1, when using the Wait > Check Exists instead of the Wait > Web Check Exists stage and condition combination, a non-repairable error message displayed instead of a repairable validation warning when the Application Modeller was set to A browser that is already running. A validation warning now displays regardless of the application type selected in Application Modeller.


Control Room

Description of change


Previously in Blue Prism versions 6.10.0 to 7.1.1, when a runtime resource that was a pool controller lost connectivity or went offline, it continued to attempt to act as pool controller after it was restarted. This resulted in it going offline again because another runtime resource had already assumed the pool controller role. This behavior has been updated so a runtime resource which was the previous pool controller is now added to the regular resource pool after restart and another active runtime resources assumes the role of pool controller.


Credential manager

Description of change


In previous 7.1 versions, when adding credential password properties sequentially in the Additional Properties section of the Credential Details screen, they were all saved as the last password entered. This has now been fixed so they are all saved in the order in which they were added.


Database settings

Description of change


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 script created after clicking Generate Script on the Connection Configuration screen in the Blue Prism interactive client has been updated to create the required native administrator user in the database and enable snapshot isolation. This functionality was incorrectly removed in version 7.1 when the Configure Database button was removed.


Interactive client

Description of change


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


Previously, when using the AutomateC command line to display the help in a non-English locale, for example, .\automatec.exe /locale de-DE /help, the help was incorrectly displayed in English. This has now been fixed so the AutomateC help displays in the specified locale if it is supported by Blue Prism.


Process and Object Studio

Description of change


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.


In Blue Prism 7.1.0 and 7.1.1, the interactive client or runtime resource would close unexpectedly if a Time data item was used in Process and Object Studio and the user's machine was set to a region which does not use a colon (:) as a time separator. The date/time format has been updated so this error no longer occurs in this scenario.


System manager

Description of change


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.


In previous 7.1 versions, when the Allow anonymous public Runtime Resources option was selected in System > System - Settings, updating the Runtime Resources role on the Role Membership screen under System > Security - User Roles incorrectly removed anonymous resources from the role. This prevented them from starting when the /resourcepc /public switch was used. This has now been resolved.


Browser extensions

The table below shows when each Blue Prism extension compatible with this release was introduced and the browser version against which they were evaluated. See the browser compatibility matrix for the latest browser versions evaluated.

Browser Blue Prism extension versions Date available



December 2022

Edge Chromium


December 2022



December 2022

Browser extensions release notes

Description of change


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.

BP-12472 (BP-12427)

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.


An intermittent issue has been fixed where failed attempts to automate a complex web application caused the browser to close with multiple unhandled exceptions. Any such errors are now logged and handled appropriately.


Additional components

Blue Prism API

The Blue Prism API provides a common interface for components such as Blue Prism Hub to connect with the Blue Prism database. It also provides a series of predefined capabilities that can be used by custom solutions to interact with Blue Prism programmatically using a RESTful API.

The following enhancements, minor improvements, and fixes have been made to the Blue Prism API for this release. The API reference, installation guide, and license agreement for this release can be found here.


Description of change



A new endpoint and a GET Health request has been added, which returns the health of the associated database. The request returns a value of true to indicate the database is in a healthy state, and false if it is not. This can be due to the following scenarios:

  • The database requires upgrading.

  • The database credentials are incorrect.

  • The database server is offline.




The GET requests for the endpoints have been updated to add a new duration parameter, which enables users to filter schedule logs by the schedule duration. Duration is the length of time between the start time and the end time, and is presented in the format D.HH:MM:SS. The day value is optional, and if not returned the format will be HH:MM:SS.




The GET requests for the endpoints now return a sessionCount property for the task, which enables users to retrieve the number of scheduled sessions for a task.




The GET work queue items and POST work queue items requests have been updated to return the following properties, which enable users to filter and sort using the following data:

  • sla – The time to complete the work queue item before the service level agreement (SLA) is missed. This is passed in the format DD:HH:MM:SS.

  • slaDateTime – The date and time by which the item must be completed in order to meet the SLA. It is passed in the format DD:MM:YYYY HH:MM:SS. If a work queue item is processed before this date time, it is within the SLA.

  • withinSLA – Indicates if the work queue item was completed within the SLA.

  • processName – The process name of the work queue item.

  • isSuggested – If the Director component has recommended the queue item as the next best item to process.




The POST work queue items request has been updated to add an error message when an invalid deferredDate is passed. Previously, a generic error response was returned.



Compatible Blue Prism Hub components

Authentication Server

Authentication Server provides centralized common authentication for users across three key components of the Blue Prism platform: Blue Prism Enterprise, Blue Prism API, and Blue Prism Hub. For more details, see the Authentication Server configuration guide. The following enhancements, minor improvements, and fixes have been added to the configuration of Authentication Server in Blue Prism Enterprise for this release:

Description of change


The following optional switch and parameters have been added to the AutomateC /serverconfig command:

/serviceaccount <clientId> <clientSecret>

This enables users to specify the client ID and secret of the service account created to allow Blue Prism to communicate with Authentication Server and perform a scripted installation of Blue Prism when pointing at an Authentication Server instance, without having to use the Blue Prism Server user interface.

If these parameters are used with an existing server configuration, any existing credentials will be overwritten by the new values entered.

For more information, see Command line options.