Blue Prism Release Notes 6.5.1 - 4.Pd

6.5.
1 Release Notes
Release Notes and Upgrade Guide
Document Revision: 1.1

6.5.1 Release Notes | Release Notes and Upgrade Guide
Trademarks and copyrights
Trademarks and copyrights

The information contained in this document is the proprietary and confidential information of Blue Prism
Limited and should not be disclosed to a third-party without the written consent of an authorized Blue Prism
representative. No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying without the written permission of Blue Prism Limited.
© Blue Prism Limited, 2001 – 2019
®Blue Prism is a registered trademark of Blue Prism Limited
All trademarks are hereby acknowledged and are used to the benefit of their respective owners.
Blue Prism is not responsible for the content of external websites referenced by this document.
Blue Prism Limited, 2 Cinnamon Park, Crab Lane, Warrington, WA2 0XP, United Kingdom.
Registered in England: Reg. No. 4260035. Tel: +44 870 879 3000. Web: www.blueprism.com
Commercial in Confidence Page 2 of 82

Contents
Contents
Trademarks and copyrights 2
Contents 3
Introduction - Blue Prism version 6 5
Upgrading Blue Prism 6
Review upgrade notices 6
Applying Updates 7
Upgrading to version 6 - Selecting a server communication method 8
Database Upgrade 9
Release Notes 11
Version 6.5.1: July 2019 11
Upgrade notices 14
Upgrading from versions prior to 3.5.25 14
Upgrading from versions prior to 6.0 16
Invalid upgrade paths 20
Previous Releases 21
Version 6.5: April 2019 21
Version 6.4.3a: June 2019 32
Version 6.4.2: February 2019 34
Version 6.4.1: January 2019 37
Version 6.4: November 2018 39
Version 6.3.2: November 2018 45
Version 6.3.1: October 2018 47
Version 6.3: August 2018 49
Version 6.2.2: October 2018 60
Version 6.2.1: May 2018 62
Version 6.2: February 2018 65
Version 6.1: October 2017 70

Contents
Version 6.0: September 2017 75

Introduction - Blue Prism version 6
Introduction - Blue Prism version 6

Effective digital strategies require a connected Enterprise where technologies such as artificial intelligence
(AI), machine learning and sentiment analysis easily integrate with business operations to deliver value. The
Blue Prism v6 series serves as the “Operating System for the Digital Workforce” to bring your digital strategies
to life fast and securely with Robotic Process Automation (RPA) that is:
• Intelligent - Robots that understand context, derive meaning & anticipate change
• Connected - Bringing people, machines & processes together with “best of breed” technologies
• Easy-to-Control - Flexible 24/7 capability with full visibility, control & absolute compliance
Our approach enables Blue Prism to provide the backbone of your digital strategy. Blue Prism v6 has been
developed alongside over 400 customers, leveraging best-of-breed technologies to provide a digital workforce
that offers the most productivity, adaptability, scalability and security. The following serves as the Release
Notes and Upgrade Guide to this release of Blue Prism.

Upgrading Blue Prism
Upgrading Blue Prism

The Blue Prism update process is designed to be both flexible and simple and as such it is possible to
upgrade directly from one version of Blue Prism to a newer version without needing to step-through each
intermediate update. E.g. a system can be updated directly from v4.2.5 to the latest version.
Applying updates to Blue Prism should include the following steps prior to updating production
environments:
1. Review the associated Release Notes, available via the User Portal. The notes contain a summary of the
fixes and product enhancements included in a given release.
2. Using the Release Notes, verify if there are any special notices relating to the upgrade path being
followed (e.g. if there are known actions that are required as part of the upgrade being applied; if a
new license key is required; if an update to Login Agent is required; or any known implications).
3. Take a backup of the Blue Prism Database(s).
4. Apply the update to Dev and Test environments to validate the appropriate processing of designed
processes (functional and non-functional verification is recommended). Non-functional testing could
include reviewing the average handling time of core processes before and after the update has been
applied.
5. Optionally, and where relevant, update existing processes to take account of new or improved features
if these are desired and carry out appropriate testing. Where this includes importing the latest version
of provided VBOs, all processes which reference these should be re-verified.
If assistance is required, please contact Blue Prism Product Support (support@blueprism.com).
Review upgrade notices

Special considerations are required when upgrading from versions prior to those listed below:
• 3.5.25
• 4.2.16
• 4.2.35
• 5.0.5
• 5.0.23
• 5.0.24
• 5.0.29
• 6.0
• 6.3
• 6.4.2
• 6.5
For example, if a deployment currently running 5.0.21 is being upgraded to Version 6.1, it is essential that the
information for updates prior to 5.0.23, 5.0.24, 5.0.29, and 6.0 are followed.
For example, if a deployment currently running 5.0.21 is being upgraded to Version 5.0.29, it is essential that
the information for updates prior to 5.0.23 and 5.0.24 are followed.
For full information about the considerations when upgrading from these versions, see Update notices.

Applying Updates
Applying Updates
The recommended procedure for applying updates to a given environment is as follows:
1. Stop any currently executing processes or schedules.
2. Close or exit all connected Blue Prism clients (e.g. Interactive Clients, Runtime Resources, Blue Prism
Server).
3. Back up the database (data files and transaction logs).
4. Install the new version by executing the supplied MSI installer on all devices. Commonly there is no
requirement to remove a previous version first - review the Update Notices to verify if the upgrade
path being followed does require the previous version to be uninstalled prior to a new version being
applied. Subject to use of application distribution software, this task could be fully automated.
5. If there are database changes for the upgrade path (this is indicated in the Release Notes) these can
either be applied via an in-product option, or through use of SQL Upgrade Script that is applied
manually.
The database changes will need to be applied to each environment affected by the update. (See
following section for details).
To upgrade a database using the in-product capability, or by directly applying the upgrade script, a
SQL user account with the following permission is required: sysadmin (server role) or dbowner
(database role)
6. Once any required changes have been applied on one client, use the various connections to log into
each of the Blue Prism environments to validate the installation and check that there are no more on-
screen messages.
7. If Login Agent is used within the environment and it is necessary to apply an updated version (this is
indicated in the Release Notes) it should be installed by executing the supplied MSI installer on all
appropriate devices.
Once Blue Prism has been installed the Login Agent installation files can be found within an Installers
folder within the Blue Prism install location.
8. Following the update of Login Agent, install the updated Login Agent Blue Prism Release into the
relevant environment and ensure that the relevant processes reference the updated Login Agent VBO.
9. Start the Blue Prism Server service on each Blue Prism Server and resume all Blue Prism clients.

Applying Updates
Upgrading to version 6 - Selecting a server communication method

Blue Prism version 6 offers a number of .NET and WCF communication methods:
• .NET Remoting Insecure
• .NET Remoting Secure
• WCF Insecure
• WCF: SOAP with Transport Encryption
• WCF: SOAP with Transport Encryption & Windows Authentication
• WCF: SOAP with Message Encryption & Windows Authentication
Consult your Security and Governance team, Network Administrators, and Server Support staff to help select
the best option for the needs of your business.
Follow the steps below to change the server communication method.
A successful upgrade must be completed and verified prior to updating the server communication method.
1. Select an appropriate communication method which aligns with the deployment architecture.
2. If using a WCF method with Transport Encryption, generate the required server certificate per server.
3. Stop all component devices.
4. Make the necessary server configuration changes.
5. Start the server.
6. Update the connection settings on all components.

Applying Updates
Database Upgrade
The database upgrade can be applied either via:
• An in-product option, or
• Through use of SQL Upgrade Script that is applied manually.
In-product upgrade
On a single client (typically the Application Server), click File > Connections. Ensure the relevant connection
is selected and click Upgrade Database.
The connection to the database will require necessary database permissions to carry out the required
changes. For full details of the required permissions, see Applying Updates.

Applying Updates
Directly executed SQL Script (advanced)

The SQL upgrade script for the relevant Blue Prism version must be applied against all databases which are
to be upgraded.
Once the database upgrade script has been executed against the relevant databases, the following command
must be run against each of the affected Blue Prism environments from a single client (typically the
Application Server).
• Single Sign-On - automatec.exe /refreshdependencies /dbconname “[DBConName]” /sso
• Blue Prism Native Authentication - automatec.exe /refreshdependencies /dbconname
“[DBConName]” /user [Username] [Password]
• DBConnName - The name of the Blue Prism Connection (as displayed within the client interface
on the device where the command is being executed).
• Username - The username used to log into the environment accessed using the specified Blue
Prism Connection (only required where not using single sign-on for the Blue Prism platform).
• Password - The password used to log into the environment accessed using the specified Blue
Prism Connection (only required where not using single sign-on for the Blue Prism platform).

Release Notes
Release Notes
Version 6.5.1: July 2019
Notices
Database Changes This release requires the Blue Prism database to be version 318.
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.5.
Browser extension • Chrome browser extension 2.0.0.1 - the latest version of Chrome the
extension has been evaluated against is 75.0.3770.142.
• Firefox browser extension 6.5.0.12573 - the latest version of Firefox the
extension has been evaluated against is 68.0. The latest version that is
compatible is 67.
Important Notices Firefox version 68, launched in April 2019, has known compatibility issues with
all versions of the Blue Prism Firefox browser extension. For further information
and help working around the issue, see the following knowledge base article:
http://portal.blueprism.com/customer-support/support-center#/path/1359592082
Certifications
This release has been verified as complying with the below standards by Veracode – an independent
application security organization.
Static Code Analysis VL5. Veracode Score: 100/100. Further information

PCI DSS PCI DSS Version 3.2 compliant in sections 6.1, 6.3.2, 6.5, 6.6, and 11.3.2
PCI PA-DSS PCI PA-DSS Version 3.2 Sections 5.1.4, 5.2, 7.1.1, 7.1.2, and 7.1.3.
HIPAA Controls: 01.v, 02.e, 04.a, 06.d, 10.a, 10.b, 10.l, 10.m
OWASP Further information
SANS Top 25 Further information
CERT Secure Coding Further information
A compliance highlight summary report is available upon request via Product Support.

Release Notes
Fixes and minor improvements

The following fixes and minor improvements are introduced with this version.
Description of change Reference

An issue, introduced in version 6.5, that prevented custom filters being applied to the Tags and bg-3284
Resources columns in the Queue Management pane of Control Room has been addressed.
The following changes have been introduced to improve performance when opening objects us-4434
and processes in Studio: bg-3393
• The number of database calls has been reduced
• XML compression has been introduced on the application server
When changing connections in the interactive client, the permissions cache is now reloaded. bg-3308
This ensures that users transitioning to another existing database on the same version of Blue
Prism will no longer experience database-related foreign key constraint errors.
The management of connections has been enhanced to address a port exhaustion error that bg-3252
occurred due to resource connections not being closed gracefully. This resulted in ports not
being made available, which prevented interactive clients and the scheduler from successfully
connecting to runtime resources.
If a work queue item is locked at the end of a session, the cleanup process now automatically us-4803
generates a retry and schedules the item for reprocessing if the retry limit has not been
exceeded.
This mirrors the functionality of pre-6.5 versions of Blue Prism. In version 6.5, bg-598 changed
this behavior so that such items were marked as an exception but did not generate a retry.
When adding an action stage to a process, making a selection from the Action drop-down no bg-3388
longer causes Blue Prism to become unresponsive if a stage name has not been entered prior
to selecting the action.
This issue affected clients that were connected to an application server where the database
contained a large number of objects and only occurred the first time an action stage was
opened in an instance of Process Studio.
Upgrading Blue Prism to version 6.5 could result in a key constraint error if a previous database bg-3315
upgrade failed and the transaction was rolled back. This issue has now been resolved.
An issue that prevented objects and processes from being opened if they referenced a process bg-3658
that had subsequently been deleted, has been resolved.
Users can no longer run a process in Control Room if the process references a business object bg-3453
that they do not have permission to execute.
When importing a release that includes a published process, if a published process with the bg-3285
same name already exists on the database, the status is no longer incorrectly changed to
unpublished.

Release Notes
Login Agent
The installers for the latest version of Login Agent, at the time that this Blue Prism release was made
available, are provided in the Installers folder within the Blue Prism install location.
There are no applicable changes with this version of Blue Prism.
Login Agent Sample Processes and Visual Business Object updates
Visual Business Object Updates


Upgrade notices
Upgrade notices
Please review the following notices according to the version of Blue Prism which you are upgrading from.
For example, if a deployment currently running 5.0.21 is being upgraded to Version 6.1 it is essential that the
information for updates prior to 5.0.23, 5.0.24, 5.0.29 and 6.0 are followed.
As with all upgrades it is essential that a full and verified database backup is performed prior to applying the
database upgrades.
Upgrading from versions prior to 3.5.25

Manually disassociate certain security roles prior to upgrade
If upgrading from a version prior to 3.5.25, there are a number of security roles that must be manually
disassociated from any of the users from within the Users area (System Manager – Security) prior to carrying
out the upgrade. The roles which much be disassociated are: Process Designer, Business Object Designer and
Observer
The Blue Prism Server service must be manually deleted

If a Blue Prism Server has been deployed as a Windows Service, it is also necessary to delete the Blue Prism
Server key from within the registry on that machine.
• Launch the registry editor, REGEDIT
• Search for: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
• Locate the Blue Prism Server Key
• Delete that key and all sub-keys

Previous License keys will not work
This version introduces a new format of license key therefore a new key must be obtained prior to upgrading.
These can be requested via your Blue Prism Account Manager.

Blue Prism Web services need to be re-exposed
This version introduces a new method of exposing processes and objects as Web Services. Therefore, if
upgrading from an earlier version it is necessary for any Blue Prism Processes or Objects which should be
available as a web service to be explicitly exposed using the new methods following the upgrade.
For more information, see the Blue Prism User Guide – Web Services, available from the Blue Prism Portal.

Upgrade notices

Recommended steps:
Prior to applying the update, generate a Roles report – this may be useful if there is a requirement to verify
user permissions variation prior to and following the update. (System > Reports > Roles: Generate).
Required steps:
• Blue Prism v5.0 is built on .NET Framework 4, and therefore all components (Interactive Clients,
Runtime Resources, and Application Server) will require .NET 4 to be installed as a pre-requisite.
• A new license key will be required. This can be obtained via your Blue Prism Account Manager.
Control room permissions are automatically enforced for the command line
Blue Prism v4.2.43 introduced an optional setting that would enforce control room permissions when
interacting with Blue Prism processes via the command line. In v5.0 this option is enforced meaning that
when interacting with processes programmatically via the command line the user requires the permission
named Full access to session management.
Dashboards require users to have increased SQL permissions

Where the SQL account used for user access to the database has restricted access (i.e. where it is not a
dbowner or similar), the security permissions for this account may need to be extended for the Management
Dashboards to function correctly as these leverage stored procedures. Blue Prism provides a number of SQL
Security roles which provide the execute privilege for the necessary stored procedures which can be
allocated to these users if appropriate. These roles are: bpa_ExecuteSP_DataSource_bpSystem, bpa_
ExecuteSP_DataSource_custom, bpa_ExecuteSP_System.
Increased SQL disk space is required and Unicode logging is disabled by default
Blue Prism version 5.0 provides the capability to store information presented in any language by introducing
support for storing Unicode characters within the database. Unicode characters require increased amounts of
disk storage in comparison to ASCII.
Users with a large number of work queue items in their database may wish to review their storage
requirements prior to upgrading due to the increased storage space required.
Unicode support is enabled automatically throughout the product with the exception of Session Logging (i.e.
the logging which takes place as processes execute). If Unicode support is required for Session Logging this
can be enabled manually within System settings.
Prior to enabling Unicode support for the Session Logs, the amount of available disk space should be
considered in line with the current log retention and archiving strategy. Additionally, features such as SQL
Unicode Compression (if available) can be utilized to minimize the disk space required.
Previous License keys will not work

This version introduces a new format of license key therefore a new key must be obtained prior to upgrading.
These can be requested via your Blue Prism Account Manager.
Requires .NET Framework 4

Blue Prism v5.0 is built on .NET Framework 4, and therefore all components (Interactive Clients, Runtime
Resources, and Application Server) will require .NET 4 to be installed as a pre-requisite.

Upgrade notices

Login Agent should also be upgraded
While they continue to be supported, it is strongly recommended that previous versions of Login Agent are
replaced with Login Agent 5.0.23 when using Blue Prism 5.0.23 to enable the features provided in Login Agent
5.0.23 to be realized.

Single sign-on settings need to be re-verified.
When upgrading from a previous version that was configured to use Blue Prism Single Sign-on it is necessary
to re-validate the single sign-on settings once this version has been installed.

Downgrading to earlier versions will require reconfiguration.
Downgrading a device that has been installed with 5.0.29 (or above) to an earlier version will result in Blue
Prism being unable to correctly read local configuration files. The re-configuration will require manual
intervention.
Upgrading from versions prior to 6.0

Requires .NET Framework 4.7
All components (Interactive Clients, Runtime Resources, and Application Server) will require .NET 4.7 to be
installed as a pre-requisite.
Introduces WCF (Windows Communication Foundation)

Alternative server communication methods have been introduced, in addition to .NET remoting. Following a
successful upgrade, it is recommended that one of the new WCF communication methods is chosen. WCF
connection modes require session persistence to be enabled. If existing load balancing is configured that
does not apply session persistence, re-configuration will be required.
Dates are now processed using different logic

The logic used to interpret dates and times has changed and it is important that all processes that use date
and times, particularly those that use collections with code stages are re-validated and updated accordingly.
See the release notes for details, and the v6 Data Sheet – Date and Time Handling available on the portal for
full information on the changes and implications. Aesthetic changes are also included. For example: Session
Logs are now saved and displayed in Resource Local time; and the Process Alert history is now stored in UTC
and displayed in Client Local time.

Upgrade notices
Pending or Running sessions should be completed or cancelled prior to upgrade

Process automations that are in a running or pending state should be completed or otherwise stopped or
cancelled prior to upgrading to avoid issues resulting from updated date/time handling logic. Tesseract
language packs will need to be updated on all devices
Tesseract Language Packs that are compatible with Tesseract 3.05.01 will need to be deployed to all devices
that use Tesseract with language packs. The files can be downloaded from the Tesseract product site:
https://github.com/tesseract-ocr/tesseract/wiki/Data-Files.
A new installer has been introduced

A new Blue Prism installer was introduced in version 6.0 that brought about changes to the scripted install
procedures. See the v6 User Guide – Installing Enterprise Edition for further details.

Multi-team Environments (Group-based Permissions) – validate permission assign-
ment
The allocation of permissions is now more granular, and a number of new permissions have been provided.
To ease upgrades, all pre-existing user roles are automatically expanded to include these selected new roles:
Execute (Objects/Processes); Execute (Objects/Processes) as Web Services; Authenticate as Resource. For new
deployments, these permissions are only added to the appropriate security roles.
The assignment of all permissions must be reviewed to ensure they are appropriate for impacted users.
Process Administrator role permissions
Before upgrading, check that the following permissions are not assigned to the default Process Administrator
role:
• Object Studio > Test Business Object
• Process Studio > Test Process
If these permissions are assigned to the role, remove them in System > Security > User Roles, before
upgrading to version 6.3 or above.
Following a successful upgrade, the Process Administrator role is granted equivalent permissions.
New Default groups for Objects and Processes

During an upgrade to 6.3, new Default groups are added to the navigation trees in Object Studio and Process
Studio. Before upgrading, any existing group named Default that contains one or more subgroups must be
renamed.
New permission required to call Objects or Processes exposed as Web Services

A new permission, Execute as Web Service is required to call an Object or Process exposed as a Web Service.
Some programmatic options will no longer work by default

A number of session management commands (create, start, delete) no longer work by default. They have
been superseded by createas, startas and deleteas which require the use of the getauthtoken method.
While not recommended, the previous methods can be re-enabled by disabling the new setting that enforces
permissions of controlling users when carrying out session management actions.

Upgrade notices
New mechanism for securing access to Runtime Resources

The Access Rights option added to the context menu for Resource groups replaces the previous method of
applying permissions to individual Resources in System Manager. The new folder-based mechanism aligns
with the newly introduced mechanism for securing Objects and Process and additionally provides greater
control.
Items that were secured using the old mechanism must be manually re-secured using the new one.

Allow Snapshot Isolation automatically applied when using in-product capability for
creating or upgrading databases
When upgrading or creating a database, using the in-product capabilities, the Allow Snapshot Isolation
setting is now automatically applied for new and upgraded databases by default provided that the user
upgrading or creating the database has the Alter Database SQL permission. When performing an upgrade, it is
possible that a user may not have this permission and as a result, snapshot isolation will not be enabled. In
such circumstances the upgrade will still be performed but when attempting to log in or start a blue prism
server service, a message will inform the user that snapshot isolation must be enabled before a connection to
the database can be made.
To manually enable snapshot isolation after database creation or upgrade, a user with alter database
permissions must run the following command:
ALTER DATABASE [%%dbasename%%] SET ALLOW_SNAPSHOT_ISOLATION ON
Snapshot isolation must by manually applied if using a script to create or upgrade a

database
When creating or upgrading a database using a script, it is necessary to manually apply the Allow Snapshot
Isolation setting to the database.
To manually enable snapshot isolation after database creation or upgrade, a user with alter database
permissions must run the following command:
ALTER DATABASE [%%dbasename%%] SET ALLOW_SNAPSHOT_ISOLATION ON

Upgrade notices

The View Server State database permission is required to perform upgrades through the
Blue Prism user interface
As part of the upgrade process, the size of the session log tables are now checked to determine the
appropriate migration option. This change means users performing an upgrade through the Blue Prism user
interface must have the View Server State database permission. This permission is not required if upgrading
Blue Prism using a generated script.
Session logs are not migrated by default

When performing an upgrade, select whether session log data is migrated to new database tables or retained
in existing ones. Depending on the volume of session log data, migration can be performed during the
upgrade via the user interface or post-upgrade using a tool available from Blue Prism Customer Support.
To streamline the upgrade process, session logs should be archived before upgrading. By default, sessions
logs that remain in the system will not be visible after upgrade but can still be migrated when required.
The following options display when Upgrade Database is selected from the Connection Configuration dialog:
• Upgrade database and retain session logs in existing tables - The new database tables are created
during the upgrade but session log data remains in the existing tables. This is the default option and
provides the recommended upgrade path, ensuring upgrades are performed more quickly. The existing
session log table names are suffixed with '_pre65'. The data from these tables is not be visible in
session management but can still be migrated using the tool, available from Blue Prism Customer
Support.
• Upgrade database and migrate existing session log data to new tables - Data from session logs is
migrated to new database tables during the upgrade. As the migration can take some time, this option
is not available for environments with more than 10 million session logs or 10GB of data and is not
recommended for environments with more than 1 million session logs.
When generating upgrade scripts using the 'Generate Script' button, the created script will run the upgrade
without migrating session logs.
Tesseract language packs must be updated

The Tesseract OCR engine has been upgraded to version 4.0 and is applied to all installations of Blue Prism
6.5. Any non-English language packs from versions prior to 6.5 will no longer work and new ones must be
installed.
If required, Blue Prism 6.5 can be configured to use previous versions of Tesseract. For further information,
see the v6.5 User Guide - Feature Summary, available from the Blue Prism Portal.
Unicode logging must be enabled for Chinese and Japanese versions of Blue Prism
To ensure that process logs are correctly audited in Simplified Chinese and Japanese language versions of
Blue Prism, select Enable Unicode support for session logs in System > Settings.

Upgrade notices
Invalid upgrade paths

Occasionally features are made available both within the latest version of Blue Prism and also previous
editions of the software. Where the changes have certain characteristics, it is necessary to prevent certain
upgrade paths to protect data integrity.
The restriction is applied when applying the database update. The user carrying out the action will be
advised that the database cannot be upgraded as it is newer than the required database.
Applies to Notes
environments
currently using
4.2.56+ The minimum Version 5 upgrade is 5.0.11, which is the first applicable version that
contains the Encryption Schemes and AES-256 support provided in this version of 4.2.
4.2.57+ The minimum Version 5 upgrade is 5.0.12, which is the first applicable that contains
the option to configure the inter-component communication to use FQDN host
names.
4.2.61+ The minimum Version 5 upgrade is 5.0.18, which is the first applicable version that
contains aligned work queue optimizations.
5.0.34 The minimum Version 6 upgrade is 6.1, which is the first applicable version that
contains a number of items also featured in 5.0.34.
5.0.35 The minimum upgrade is 6.4.
6.2.2 The minimum upgrade is 6.4.
6.4.3 The minimum upgrade is 6.5.1.

Previous Releases
Previous Releases
Version 6.5: April 2019
Notices
Database Version This release requires the Blue Prism database to be version 318.
Login Agent Login Agent has been updated for the 6.5 release.
Browser extension At the time of this release, the latest Blue Prism browser extension versions are:
• Chrome browser extension 2.0.0.1 - the latest version of Chrome the
extension has been evaluated against is 66.0.3.
Important Notices To streamline the upgrade process, session logs should be archived before
upgrading. By default, sessions logs remaining in the system will no longer be
visible after upgrade. However, they can still be processed using the archiving
tool once the upgrade is complete. For lower volumes of sessions logs there is
an option to update the records as part of the upgrade so that they remain
visible.
As part of the upgrade process, the size of the session log tables are now
checked to determine the appropriate migration option. This change means
users performing an upgrade through the Blue Prism user interface must have
the View Server State database permission.
The Tesseract version has been updated to 4.0 and ships with new English
language packs. Any non-English language packs from versions prior to 6.5 will
no longer work and new ones must be installed on each device where Tesseract
will be used.
It is essential that the upgrade notices are reviewed before applying this release.
Certifications
Static Code Analysis VL5 + SCA. Veracode Score: 100/100. Further information

Previous Releases
Enhancements
The following new features and enhancements are introduced in this version of Blue Prism.

Data Gateways provides a centralized mechanism for pushing data out of Blue Prism for use in ep-146
external systems for monitoring and reporting, long-term data storage, and to feed machine us-3694
learning models. System Settings are applied to determine what data will be processed by the
Logstash Powered Data Gateways engine, and a configuration defines the outputs to which
data will be pushed. Data from session logs, published dashboards, and process stages can be
sent to a variety of external outputs - HTTP endpoints, external databases, third-party analysis
tools, and flat files - providing flexibility and control over data analytics and storage.
Three new user permissions have been introduced for this feature and provide the necessary
rights for regular and advanced configuration, and for managing the Data Gateways engine in
the Control Room.
To support this feature, the new Data Gateways internal VBO is now available. It has one
action, Send Custom Data, that accepts collections as inputs and sends the data from those
collections to the Data Gateways engine.
A number of additional components are required for Data Gateways that are available in a
separate installer, Blue Prism Data Gateways Components, available from the Blue Prism Portal.
Data Gateways requires a SQL native user to be created against the Blue Prism database and
is only available for Blue Prism databases that can support this.
For full instructions on how to configure and use data gateways see the v6.5 User Guide - Data
Gateways, available from the Blue Prism Portal.
The Work Queue Snapshots feature allows metrics relating to work queue performance to be ep-147
externalized, making it available to business intelligence tools and other reporting software to
gain an insight into work queue item and exception volumes. Configurations determine which
queues are included in each snapshot and at what frequency the data is captured. Snapshots
can then be compared to identify trends and provide a better understanding of queue
performance.
Additionally, two new in-product data sources have been introduced which show some of the
information in dashboard tiles.
The Blue Prism interactive client user interface and product help are now available in Japanese ep-30
and Simplified Chinese. When starting Blue Prism, the user interface is automatically presented us-3759
in the locale of the operating system for the supported language. The required language can
also be selected from the login screen.
As part of this enhancement, public holidays for China, Japan, Hong Kong, and the USA are
now available in calendars by selecting the required region in the System > Calendar settings.
Support for IPv6 connections has been introduced, allowing Blue Prism to be deployed in ep-97
environments that utilize IPv6 network protocols for all connections as well as those that use a
combination of IPv4 and IPv6.
For more information, see the v6.5 Data Sheet - Blue Prism Network Connectivity.

Previous Releases

The Tesseract OCR engine has been upgraded to V4.0.0 and is applied to all installations of us-3972
Blue Prism 6.5. us-3120
New options have been added to the system settings that allow users to select select which
characteristics of the V4.0.0 engine will be applied.
For further information, see the upgrade notices and the v6.5 User Guide - Feature Summary,
available from the Blue Prism Portal.
A new option has been added to the Recover stage properties dialog that applies a limit to the us-3537
number of times a Recover stage can be executed. It is no longer necessary to use additional
stages to count the number of tries.
The number of times the Recover stage has been called is reset when the Start stage of the
page on which it resides is executed.
The Resolve Import Conflicts screen has been improved so that conflicts discovered during an bg-502
import are presented in a grid view.
A new user permission - Release Manager - Import Release - has been introduced. To import a us-3847
release in Release Manager, a user must have this permission as well as the relevant us-3783
permissions for all the components in that release, such as Import Process, Import Tile etc. This
applied both when importing from the File menu, or using the command line.
For new installations, the permission is applied to the built-in System Administrator and
Release Manager roles. For upgrades the permission is automatically applied to any user role
that already has the View Release Manager permission assigned.
Additionally, the enforcement of import permissions is now repeated on the application server.
Stage names are now automatically assigned a default name that reflects the selected action us-3544
for scenarios when a name is not manually entered by the user. us-3699
When creating a copy of an object or process using the Save as option, users are now us-2702
presented with a list of destination folders for which they have create permissions.
A new tile, Hours Spent Working Queues, is available for use in dashboards. The tile displays the us-3075
hours that runtime resource spent working queues in each month during a specified period of
time.
The following improvements have been made to Blue Prism auditing functionality: us-3547
• Paging and sorting controls have been added to the Process Logs and Audit Logs screens us-454
to improve navigation. bg-1599
• Audit log entries are now created when environment variables are added, edited, and bg-1926
deleted from the within the System tab.
• Toggling the System Setting, Personal Runtime Start Up, now produces an accurate audit
log message.
• An issue that incorrectly added events to the audit log when the System > Settings page
was opened has been addressed. The raised events suggested that a user had changed a
setting when no updates had been made.

Previous Releases

The following improvements have been made to scheduling: bg-2038
• It is now possible to use process alerts with schedules. Previously, when alerts were bg-2451
enabled and a schedule that would generate an alert was triggered, an error was bg-2478
produced.
• The way in which schedules are retrieved from a database has been optimized to
improve performance by only holding database connections open whilst schedule data
is retrieved.
• Where the scheduler was enabled on an application server, unnecessary connection
attempts were being made to private resources. A change has been implemented to
prevent such connection attempts as servers do not have permission to run schedules
on private resources and are therefore not required.
A number of updates have been made to the license management utility: ep-143
• Standalone licenses that cannot be used in conjunction with other licenses can now be bg-2472
added us-1551
• Licenses that require activation can now be added and activated using a new wizard bg-2683
• License validation now ensures that, when using multiple licenses, each one is unique
• The Installed Licenses screen now takes into account any license added or removed by
another client in the same environment to prevent licenses being inadvertently removed
when two users on different clients are editing licenses at the same time.
The following changes have been made to improve the process of upgrading and creating us-3739
databases: us-3698
• A 'Generate Script' button is now available when creating and upgrading databases
through the Connection Configuration dialog that produces the associated database
scripts.
• During database creation or upgrade, a progress bar now displays to inform users of the
status of the upgrade and show the script that is currently running.
The progress bar may pause during while large operations.
When performing an upgrade to version 6.5 or above, users are given the option to migrate us-3904
session logs to tables that provide higher performance. If the option to migrate is not chosen us-3906
data will be left in the current tables. This reduces the need for a lengthy upgrade process and
us-4017
allows session log data to be migrated post-upgrade using a tool available from Customer
Support.
For more information, see the Upgrade Notices for version 6.5.
Enhanced application level logging functionality has been added to Blue Prism so that, once us-699
enabled, more detailed information about application execution and performance can be
accessed to assist when troubleshooting.
For further information, see the Troubleshooting - Logging topic in the in-product help.
A new option has been added to the Blue Prism installer - Google Sheets Automation - that us-2531
installs the DLLs required to interact with spreadsheets, presented in Google Sheets, via the
new VBO.

Previous Releases

The following changes have been made to the System > Workflow > Environment Locks screen: us-3549
• Pagination has been introduced to improve navigation
• The default filter for the Lock Time column has been changed from All to Today.


The following changes have been implemented in the Control Room: bg-2381
• Performance has been improved when accessing the control room by ensuring the data us-1712
required for saved and selected session filters is only requested once. bg-2685
• The Control Room > Session Management screen has been updated so that retired bg-2731
processes are no longer available from the Process filter drop-down.
• An issue that caused the User filter in Control Room > Session Management to be
incorrectly applied, has been addressed.
The following improvements have been made to the Blue Prism Skills feature: us-3623
• When deleting a Skill, any associated Web API is now automatically deleted, providing it bg-2385
is not associated with any other Skill.
• The System > Skills > Management screen has been updated so that the format of the
Delete and Find References options are consistent with similar controls in the Blue Prism
user interface.
• The Skills toolbar incorrectly rendered when re-sized if the scale and layout size was
greater than 100% and the Fix Scaling for apps Windows setting was applied. This issue
has now been addressed so that the toolbar renders correctly regardless of the layout
size.
The following changes have been made to improve functionality when using Blue Prism with bg-2391
Japanese language characters and Windows versions: bg-1779
• It is now possible to input Japanese characters into a browser application in Chrome bg-620
using a Write stage.
• An issue that prevented the keyboard entry of Japanese characters into embedded text
boxes within a number of stages in Object Studio and Process Studio, has been resolved.
• An issue that caused the wrong window tile to be spied in Unicode applications when
using the Japanese language version of Windows has been addressed so that the
intended window tiles are now successfully spied.
The auto-archiving feature has been updated to work more effectively in environments with us-3546
high volumes of data.
If a work queue item is locked at the end of a session, the cleanup process now only marks the bg-598
item with an exception. Previously this scenario would automatically create a retry for the
queue item.

Previous Releases

In the Queue Management screen, applying filters of less than 12 hours in the Created column bg-2117
for work queue items was causing all data to be cleared from the table if used in anything
other than the local time zone. This issue has been addressed and the filters in work queues
now work correctly, regardless of the time zones.
A change has been implemented to address an issue that produced errors when displaying bg-2392
active queues over WCF connections if two control room users attempted to simultaneously
change the number of target sessions for a given queue.
An change has been implemented to ensure that carriage returns and line feeds in command bg-160
replies from Runtime Resources that are configured to use an SSL certificate are processed
correctly by the interactive client and scheduler.
The Session Log viewer UI has been updated to add maximize and minimize buttons and bg-543
remove the help button.
The Manage Access Rights screen for object and process groups has been updated to stop bg-2353
changes to the Unrestricted/Restricted options being saved if the user clicks Cancel or the X
button.
The following improvements have been made to the Blue Prism browser extensions: us-3418
• The Chrome and Firefox browser extensions have been updated to improve resilience bg-2727
and stability when attempting to make a connection to a website. bg-2612
• Get Path data is now available on elements in read stages. bg-2624
• An issue that caused an out-of-memory exception to occur when running processes and
objects that automated applications or web pages presented in Chrome or Firefox has
been addressed.
• An update has been made to the Firefox browser extension to address an issue that
prevented the Application Modeller from attaching to instances of Firefox that were
already running.
A warning message now displays when a user attempts to log in to an environment configured bg-1657
with single sign-on for Blue Prism that has an inaccessible domain.
The Startup Parameters dialog now correctly displays when accessed from the Debug menu in bg-2005
process studio. Previously, attempting to access startup parameters in this way, resulted in an
error.
When attempting to edit a locked process from a process stage, users are asked if they want to bg-2432
open the process as view-only instead. Previously, if the user selected 'No' an error would be
thrown. This issue has now been addressed and this action now closes the message box.
An issue that prevented processes being renamed on import if the process had the same name bg-2467
as an existing business object has been addressed.
The default value for the Stage logging setting in internal business objects is now Error Only. us-3534
This applies to all internal business objects apart from Get Next Item in the Work Queues
Business Object, for which the default value remains Enabled.
The Find References functionality in Object Studio now correctly returns references to other bg-2157
actions in the same object that are called from page and action stages. Previously, finding
references under these circumstances did not produce any results.

Previous Releases

For published objects and processes for which a user does not have edit permissions, the bg-2519
Publish to Control Room check box can no longer be toggled. This is a cosmetic change as,
although the user could previously interact with the check box, their permissions prevented
them from saving any changes.
An issue that produced an error when attempting to save a collection that contained multiple bg-1180
nested collections with the same name, has been addressed.
It is now possible to save a collection that contains multiple nested collections that have the
same name. Previously, attempting to save under these circumstances would result in an error.
An issue whereby some column headers in large nested collections were not being displayed, bg-643
has been resolved.
An issue that produced an error when attempting to open application modeller after stepping bg-506
into a child object in a process, has been addressed. bg-275
A further change in this area has been implemented to ensure that, when stepping into a stage
that uses a shared application model, the parent object is correctly initialized before being
called.
An issue that produced an error when attempting to save changes to previously spied elements bg-2096
caused the edited elements to be removed from the Application Modeller. This issue has now
been resolved and such changes can now be successfully saved.
When editing a child object that used a shared application model, changes to non-text bg-2412
attributes were not saved and therefore did not update the parent model. This issue has been
addressed so that changes to non-text attributes in child objects are now reflected in the
associated parent objects.
An issue that produced an error when copying elements from one instance of Application bg-105
Modeller to another if the first instance was closed before the element was pasted, has been
resolved.
An update has been made to ensure that, for application models configured to attach to an bg-3078
existing instance of an application, the Restrict to non-invasive automation techniques setting is
correctly applied if the application is launched after failing to attach.
Improvements have been made to resolve issues when using invasive techniques to interact bg-2171
with an application, specifically when translating coordinates for a target application that is
rendering using a different coordinate space.
The following Management Information settings, in System > Reporting, are now applied by us-3206
default for new installations of Blue Prism:
• Collect utilisation and productivity statistics
• Automatically refresh statistics daily
On upgrade, the previously applied settings are maintained.
Using the Process MI tool over WCF connections no longer results in an error. bg-2332
An update has been made to the Add a Web Service wizard so that FindByThumbprint can be bg-2293
selected as the Find Type for SSL Authentication. Previously, if FindByThumbprint was
selected, the Next button remained disabled.
A change has been implemented to ensure that when a Web API definition is configured to use bg-2394
parameters in restricted HTTP headers, the associated values are successfully passed.

Previous Releases

When adding SOAP Web Services, the WSDL definition being imported is now checked to bg-2482
ensure it does not contain unsupported data types. If unsupported data types are encountered,
the operation is cancelled.
Passwords for credentials, used for calling web services from Blue Prism, can now accept the bg-2376
colon character.
A number of improvements have been made when working with releases: bg-932
• When creating a release that contains a credential, Blue Prism incorrectly attempted to bg-2114
include the Additional Properties values of a credential, resulting in an error. This issue bg-1010
has been addressed so that no attempt is made to include this sensitive data in a
release.
• Importing a release containing a schedule that already existed in the database would fail
if the incoming schedule contained different tasks to the existing one. This behavior was
only observed when importing over a server connection. This issue has been resolved
and such releases now import successfully.
• A change has been implemented to ensure that, when importing a release, overwriting
an existing published process does not cause the maximum number processes for the
associated license to be exceeded.
A message box now displays if a user attempts to create a new database that has the name as us-903
an existing database. Users can to select whether they want to overwrite the existing database
or cancel the operation.
The Connection Settings node in the System tab now shows as being disabled to users who do bg-2548
not have the System - Web Connection Settings permission enabled for their user role.
Previously, although such users were prevented from accessing the node, it displayed as active.
If the word "Process" was included in an environment variable Name, Description, or Value bg-1876
field, it would be replaced with "Business Object" when the user navigated away from, and
returned to the System tab. This issue has been fixed so the text in environment variables
remains as entered.
In the System tab, the Web API > Connection Settings node has been renamed Web Connection bg-2588
Settings.
The System - Web Connection Settings preference has been renamed Business Objects - Web bg-2539
Connection Settings.
Debug sessions that crashed during execution, and therefore were unable to finish, are now bg-2341
automatically cleaned up during the archiving process to prevent unnecessary data being
retained in the database.
A change has been implemented to stop published custom dashboards unnecessarily refreshing bg-2505
- and therefore adding items to the event logs - if they do not contain any tiles.
An issue has been addressed that incorrectly positioned the Skills toolbar if it was opened from bg-2530
the View menu in a maximized Process Studio.
An issue that caused an error when high numbers of entries were listed in the runtime resource bg-1002
monitoring window has been addressed so older entries are removed before the limit is
exceeded.
Clicking the help icon from the Blue Prism Business Object Definitions screen now displays the bg-1024
correct help page.

Previous Releases

The way in which environmental locks are released has been optimized to improve bg-2712
performance when running multiple sessions with high volumes of data. The change prevents
the system from unnecessarily attempting to update environment locks if none are present.
Breakpoints that have the same name are now listed independently when not grouped by page bg-804
in the Breakpoint Locator. Previously, if breakpoints had duplicate names, only one entry for
that name would display in the tree.
When a pool controller is gracefully shut down, the time taken to elect a new pool controller bg-2532
has been reduced.
As part of this improvement, the timeout for keeping runtime resources alive has been reduced
from 60 seconds to 30 seconds. This ensures that the resources identify that the connection
has closed and pick up the change of controller more quickly.
Deleting pools from the System tab now immediately removes them from the control room bg-910
without the need to restart the client.
A improvement to the upgrade mechanism has been introduced so that, when upgrading from bg-1264
version 6.5 to a later release, the BP Sever service settings are not reset. This will ensure that
the configured details are maintained after an upgrade.
An issue that created intermittent errors when updating the status of runtime resources in the bg-2579
database has been resolved.
An advanced mechanism for managing the NOP communication frequency has been us-3754
introduced.
A change has been implemented to ensure users are appropriately advised when attempting to bg-2578
run AutomateC commands with an expired password.
An issue that caused an error when the /getauthtoken command was used in AutomateC.exe bg-2434
has been addressed so that the token is now correctly returned.
The /getdbdocs command has been updated to provide the expected database information. bg-2422
An issue that produced errors when creating processes over WCF: Insecure connections if bg-2452
extended logging was enabled has been addressed.
In the BPDiagnostics utility, Selecting Font > Generate from Installed Fonts no longer results in bg-2221
an error if the Arial or Comic Sans MS fonts are selected.
Serialization in exception stages has been localized so that list separators are correctly bg-2629
validated relative to the locale of the device.

Previous Releases
Login Agent
Login Agent now provides a mechanism that can allow an automatic login of a device that us-1531
requires Ctrl + Alt + Del (formally knows as Secure Attention Sequence (SAS)) to be traversed as
part of the login sequence.
In previous versions, Login Agent required the SAS to be disabled, and further attempted to
disable the setting locally for scenarios where the devices where not on a domain.
For 6.5, a new Login Agent SAS Proxy service is available which can be instructed to
programmatically submit a software SAS to the local machine as part of the configured login
process.
Additionally new, but unsupported, capabilities are provided to attempt to locally disable the
requirement to traverse the SAS and Login Message as the device reboots.
An improvement has been made to the Login Agent upgrade process to ensure that the bg-2856
connection name in the existing configuration is not overwritten.


A number of Visual Business Objects (VBOs) are provided in the Blue Prism - new or updated VBOs are listed
below. Changes within VBOs are only applied when a VBO is explicitly imported into the environment.
Any use of these VBOs should be re-verified following an import to ensure compatibility with any change of
behavior.
Object - Google Sheets

The new Google Sheets internal VBO allows Blue Prism to interact with spreadsheets in Google us-2217
Sheets to create workbooks, add data, and work with ranges. The VBO requires a local DLL to
be installed on the device where is it operating and the Blue Prism installed has been extended
to optionally place the DLL.
The VBO includes the following actions:
• Append Data - Adds the given data to a specified cell or range of cells.
• Clear Range - Clears all data from the a specified cell or range of cells.
• Get Range Values - Retrieves values or formulas from a single cell or range of cells.
• Set Range Values - Sets the values or formulas for a single cell or range of cells.
• Create Workbook - Creates a new document in Google Sheets and returns its Sheet ID.
For full instructions on how to configure and use this VBO, see the v6.5 Data Sheet- Google
Sheets VBO, available from the Blue Prism Portal.

Previous Releases
Object - MS Outlook Email

The API Documentation for this VBO has been updated to correctly state that multiple file bg-2255
paths, specified in the Attachments parameter, must be separated by semi-colons.
Object - MS Excel
The Get Worksheet Range as Collection code stage in the Excel VBO now includes an input us-3530
parameter to determine whether or not a worksheet uses a header.
The name of the output in the Save Workbook As action has been changed from Workbook to bg-2318
New Workbook Name.
Object - Work Queues

A new input parameter, Delete From All Queues, has bee added to the Delete Processed Items bg-1797
action that. When set to True, all worked items will be deleted from all work queues on the
server. Alternatively, the parameter can be used to delete all worked items from a specific
queue by entering the queue name as the value.
Utility - Locking
The Keep Environment Lock parameter has been added to the Release Lock action of this VBO. us-3540
By default, the parameter is set to false so that locks are deleted when released. If this
parameter is set to true, released environment locks are not deleted.
The parameter only affects locks created during the current session - environment locks are not
deleted when they are released.
A issue that caused an error if a value was not entered for the Comment parameter in the bg-2078
Release Lock action has been resolved. Entering a value for this parameter is now optional.
Utility - File Management

The Copy File and Move File actions have been updated to check that files exist in the specified us-3763
location before attempting to perform the action. An error is now returned if the folder is
empty.
Utility - Windows Compressed File

The new Windows Compressed File VBO allows process automations to create, delete, and us-3475
interact with compressed files. Actions in the VBO allow files to be added, deleted, and
extracted from specified .zip files.

Previous Releases
Version 6.4.3a: June 2019

Notices
Browser extension At the time of this release, the latest compatible Blue Prism browser extension
versions are:
• Firefox browser extension 6.4.3 - the latest version of Firefox the extension
has been evaluated against is 67.0.1.
Important Notices Blue Prism 6.4.3a replaces 6.4.3.
Certifications


Previous Releases


The following changes have been introduced to improve performance when opening objects us-4434
and processes in Studio: bg-3393
• The number of database calls has been reduced
• XML compression has been introduced on the application server
When changing database connections in the interactive client, the permissions cache is now us-4605
reloaded. This ensures that users transitioning between different databases on the same
version of Blue Prism will no longer experience database-related Foreign Key Constraint errors.
Login Agent

Previous Releases
Version 6.4.2: February 2019

Notices
• Firefox browser extension 6.4.2 - the latest version of Firefox the extension
has been evaluated against is 65.0.1.
Important Notices Blue Prism now requires databases to be configured to allow snapshot isolation.
Review the upgrade notices for further information, before applying this release.
Certifications

Previous Releases
Enhancements

When upgrading or creating a database, the Allow Snapshot Isolation setting is now us-3811
automatically applied. This optimizes performance when sorting and filtering sessions in us-3812
Control Room by preventing locks on the session table.
us-3813
If snapshot isolation is not applied because the user context performing an upgrade does not
us-3815
have the required permissions to apply the setting, the upgrade will still be performed but
us-3816
users will be advised that it is not possible to log in or start Blue Prism server services without
this setting being enabled.
For more information and details about how to manually enable snapshot isolation, see the
upgrade notices for 6.4.2.


An issue that prevented some users from being able to highlight and interact with elements of bg-2706
an application or web page presented in Chrome has been addressed. The issue was caused by bg-2721
an update to the Chrome browser that changed the way resources were allocated.
A number of changes have been made to improve performance in Control Room: bg-2707
• The background functionality used to sort data in the Session Management screen has bg-2708
been removed from the user interface to improve response times. As data is sorted in the bg-2729
database, this functionality is no longer required.
bg-2733
• A number of session management queries are now configured to use snapshot isolation,
bg-2736
further improving performance when sorting and filtering sessions.
us-3858
• Data to be displayed within a session view filter is only retrieved upon selection of the
us-3872
filter, as opposed to being retrieved for all filters on load of control room, improving
load time.
• An issue that prevented the correct data from being displayed when a saved session filter
was selected has been addressed so that data appropriate to the selected filter is now
displayed.
• A change has been implemented that prevents timeouts occurring when sorting high
volumes of data in the Session Management screen.
• Access times for the Session Management screen have been improved by applying a
default value of 500 to the session rows filter.
• When starting, creating, and deleting sessions, the number of calls to the database has
been optimized to improve performance when executing these actions.

Previous Releases
Login Agent


Previous Releases
Version 6.4.1: January 2019

Notices
• Chrome browser extension 1.05 - the latest version of Chrome the
extension has been evaluated against is 64.0.2.
Important Notices None.
Certifications

Previous Releases


The Chrome and Firefox browser extensions have been updated, extending coverage to us-3068
automate a number of additional websites and optimizing performance when spying such sites. bg-2623
An additional update has been made to the Firefox browser extension to address an issue that
prevented the Application Modeller from attaching to instances of Firefox that were already
running.
The Chrome extension is available for download from the Chrome Store and is compatible with
all previous versions of Blue Prism since its introduction in 6.3. The Blue Prism installer
includes the Firefox extension.
The Get Next Item action, in the Work Queues Business Object, has been updated to ensure bg-2203
only unique selections are returned where multiple machines are accessing the same work
queue. This provides assurance that, in large environments working high numbers of work
queue items, the same item will not be retrieved by two separate sessions working the same
queue.
A fix is provided to address an issue, introduced in 6.4.0, where an audit record is incorrectly bg-2506
created each time an environment lock is released. The update means that only the manual
release of an environment lock will result in an audit record being created.
A number of minor changes have been made to the translations presented when Blue Prism is us-3575
configured to display the Japanese UI.
Login Agent


Previous Releases
Version 6.4: November 2018

Notices
Browser extension The latest version of the Chrome Browser extension is 1.0.4.
The latest version of the Firefox browser extension is 6.4.0.8445.
Certifications


Previous Releases
Enhancements

Intelligent Automation Skills provide a new mechanism that enables appropriately certified ep-111
partners to build and distribute skill packages that can then easily be imported into Blue Prism
and used within a process automation. A Skills package will contain a web API definition but
can also include any number of objects, processes, and credentials to support the use of the
API definition.
The following changes have been made to Blue Prism to facilitate this change:
• A new package type of BPSKILL has been introduced that can be imported into Blue
Prism using the existing Import function.
• A new Skills > Management option has been added to the System tab that lists all
imported skills and provides controls to enable, disable, and find references.
• A Skills toolbar has been added to Object Studio and Process Studio that provides
access to all enabled skills.
A new Web API capability provides a configuration interface for natively interacting with ep-76
systems and services that provide published HTTP APIs. This allows Blue Prism to interact with
these services to either provide data to, or to consume the data or services provided by these
external systems within an automated business process. The features provided by the Web API
functionality allow the most common services to be automated by Blue Prism. Additionally,
these capabilities can be extended to cater for bespoke or more complex data structures and
authentication mechanisms, through the use of code stages.
The following changes are applied as part of this feature:
• A new Web API Services option has been added in the System tab for configuring Web
API definitions.
• A new Web Connection Settings option has been added in the System tab to enable URI-
specific connection settings to be defined.
• New credential types have been added to Credential Manager to support the
authentication methods used in API requests.
• New permissions for importing, managing, and viewing skills can be assigned to user
roles.
For more information about using and configuring the Web API Services feature, see the v6.4
User Guide – Web API Services, available from the Blue Prism portal.
A number of user actions are now subject to additional auditing. These include: ep-117
• Changes to schedules, such as updates to start and end times, and schedule frequency. us-2212
• Changes to the 'Defer to' time of a pending item. us-2213
• Updates to session variables. us-2214
• Manual archiving and restoring of sessions. us-2215
• Manual deletion and retries of queue items. us-2216
• Updates to scheduled tasks such as changes to initial values, deletion of tasks, and us-3023
adding new tasks.

Previous Releases

The existing Browser Integration functionality has been updated to include native support for ep-110
automating web pages and applications, accessed using Firefox. To facilitate this, a new us-2817
browser extension is provided that allows Blue Prism to interact with Firefox, so that business
processes that rely on interaction with this browser can easily be modelled.
As part of this feature, the Blue Prism installer has been updated to enable the installation and
removal of the extension.
For more information about the Blue Prism browser extensions, see the v6.4 Data Sheet - Native
Browser Integration for Chrome and Firefox, available from the Blue Prism portal.
A number of database improvements have been made: us-3152
• Work queues - Performance has been optimized when loading work queue data and us-3153
statistics. In addition to this, performance has been improved when working with us-3154
queries used by the following Work Queues Business Object actions:
us-3157
• Delete Processed Items
us-3161
• Get Completed Items
bg-2018
• Get Exception Items
bg-2019
• Get Locked Items
bg-2021
• Get Pending Items
bg-2027
A further improvement in this area reduces the time taken to retrieve items from a queue
bg-2085
based on Item Key filters.
bg-2086
• Schedules - Queries on schedules have been optimized to improve performance in the
bg-2087
following areas:
• Schedule triggers
• Schedule log entries
• Task sessions
A new optional setting has been added to scheduled tasks that adds an artificial delay after bg-2106
processing a task. This provides the ability to add a pause between tasks and could be used to
allow actions that affect the state of the Runtime Resource (such as Login or Log out) to
complete before subsequent actions are performed and avoid errors such as Command not
valid at this time – resource stopping.
Blue Prism can now be deployed in environments that utilize contained databases hosted on us-2821
Microsoft SQL Server. To use a contained database, the database must first be manually
created.
For further information, see the Contained databases section of the User Guide - Installing
Enterprise Edition, available from the Blue Prism portal.
A new Connection Type, SQL Server (Custom Connection String), has been added to the bg-2103
Connection Configuration screen to allow users to explicitly define the SQL connection string
to use when connecting to a supported database. This option can be used when connecting to
Azure databases using Active Directory integrated authentication.
An improvement has been made to include server information in exported schedule logs and bg-2004
timetables.

Previous Releases


The following upgrade issues have been addressed: bg-2025
• If the Process Administrator role already had the Test Process and Test Business Object bg-2063
permissions, prior to upgrading to 6.3, an error would occur whilst mapping these roles
to the latest roles introduced in 6.3.
• Users were prevented from creating new groups in the studio tree following an upgrade
due to a database permissions issue.
As part of the Multi-Team Environments feature, a Default group is automatically created at the bg-2051
top of the object and process navigation trees when upgrading from a pre-6.3 version of Blue
Prism. If the database being upgraded contains an object and/or process group called Default
that contains subgroups, the automatically created default group will be named Default (1).
This ensures the structure of the object and process hierarchy is maintained following the
upgrade.
The built-in default groups can still be easily identified by the (Default) suffix.
The default timeout that an Application Server applies when waiting for a Runtime Resource to bg-2099
respond has been increased from 10 to 60 seconds. This reduces the likelihood of Resources bg-2081
incorrectly appearing offline.
A related fix has been applied that ensures connections between an Application Server and
Resource are not unnecessarily kept open when a response from the Resource has not been
received.
Loading times have been reduced for the Schedules and Schedule Timetables screens in the bg-2020
Control tab.
Users with import permissions can now overwrite existing objects and processes when us-3030
importing a release, object, or process. Previously, the edit permission was required in
addition to import when overwriting objects and processes on import.
The dashboard tile data source list has been updated so that only custom stored procedures bg-763
prefixed “DS_” are available for selection if the schema to which it belongs matches the default
schema of the SQL account used by Blue Prism to connect to the database.
When automating Internet Explorer it is now possible to spy and interact with an element, bg-2214
displayed in an IFrame, that is hosted on a different domain to the parent site.
A number of changes have been made to improve the performance and resilience of bg-2325
environment-wide communication. bg-2326
In particular, resource availability monitoring checks no longer impede communication bg-2327
responsiveness between resources and clients. This reduces the likelihood of delays in
connecting to recently started and available resources; and reduces the likelihood of schedules
failing as a result of resources being incorrectly reported as offline.
The efficiency of connection retries to available resources has been improved to ensure bg-2330
connection attempts occur promptly following a disconnection.
Performance has been improved when creating sessions in Control Room using drag-and-drop. bg-2205

Previous Releases

The frequency of instructional connection checks from Interactive Clients and Schedulers to bg-2206
Runtime Resources has been reduced from every second to every ten seconds to improve the
efficiency of TCP communications.
The Password field in the Credential Details dialog now accepts multi-line text so items such as bg-2329
private keys and certificates can be supported.
An issue that caused the installation of Blue Prism to fail if the Default value of the Chrome bg-2346
Browser Extension registry key was already set, has been addressed.
An issue where the DBO schema was inappropriately specified in upgrade scripts has been bg-2140
resolved.
Sorting queue data in Control Room by the Resource column no longer results in an error. bg-2042
Changes have been made to the navigation tree functionality in System > Archiving to simplify us-3025
selection, ensuring the display of session logs follows a logical and consistent approach that
supports a structured audit commentary.
Filters applied in the Queues Management screen are now reflected in the output data when bg-936
queues are exported using AutomateC.
Field names that contain leading or trailing spaces can now be used in collections. Previously, bg-2138
referencing such field names in a process would cause an error.
An issue whereby a space at the end of a process name caused the archiving of session logs to bg-1771
fail has been fixed by automatically appending such process names with an underscore.
This change also introduces a check, applied when creating new processes, that prevents the
use of unsupported characters in process names.
An issue that prevented font details being captured when using the BPDiagnostics utility has bg-2213
been fixed.
An issue has been addressed that caused automations being developed or debugged in Object bg-1728
or Process Studio to get stuck in an infinite loop when stepping out of an exception on a
referenced page of a process, if the calling page contained a recovery stage to handle the
exception.
An error no longer occurs when dismissing the User Account Control elevation requests when bg-671
selecting Configure from the Blue Prism sign-on screen.
When using Blue Prism in Japanese locale, data items were incorrectly displaying in the bg-1862
Parameters pane in Code stages. Thee parameter list now loads correctly.
A fix has been applied to prevent inconsistent behavior when toggling multiple SOAP Web API bg-1826
Services in the System tab.
The /getdbdocs command has been updated to provide the expected database information us-2878
us-2567
When using Blue Prism native authentication, changing the value of the Passwords cannot bg-387
match options in the Sign-on Settings now enables the Apply button. Previously, if either
setting was updated the Apply button remained inactive.
The Web Service Consumer role has been renamed Web Service Consumers. During an upgrade, if bg-2141
a role called Web Service Consumers already exists, it is renamed Web Service Consumers bg-2142
(previous).

Previous Releases
Login Agent

A number of Visual Business Objects (VBOs) are provided in the Blue Prism release - new or updated VBOs
are listed below. Changes within VBOs are only applied when a VBO is explicitly imported into the
environment.
behavior.

When the Application Modeller is used via this VBO, the executable path is no longer pre- bg-1992
populated.

Previous Releases
Version 6.3.2: November 2018

Notices
Important Notices This release is built on version 6.3.1.
Certifications


Previous Releases


A number of changes have been made to improve the performance and resilience of bg-2325
environment-wide communication. bg-2326
In particular, resource availability monitoring checks no longer impede communication bg-2327
responsiveness between resources and clients. This reduces the likelihood of delays in
connecting to recently started and available resources; and reduces the likelihood of schedules
failing as a result of resources being incorrectly reported as offline.
The efficiency of connection retries to available resources has been improved to ensure bg-2330
connection attempts occur promptly following a disconnection.
An issue that caused the installation of Blue Prism to fail if the Default value of the Chrome bg-2302
Browser Extension registry key was already set, has been addressed.
When cloning a schedule, the Post Completion Delay value is now successfully copied to the bg-2288
new schedule.
Login Agent
available, are provided within the Installers folder within the Blue Prism install location.
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 5.0.33 and all previous versions of Blue Prism 6.

There are no applicable changes with this version of Blue Prism

There are no applicable changes to Visual Business Objects (VBOs) with this version of Blue Prism.

Previous Releases
Version 6.3.1: October 2018

Notices
Important Notices This release is built on version 6.3. Once installed, deployments featuring this
version can only be upgraded to version 6.4 or above, once available.
Certifications


Previous Releases


A new setting has been added to scheduled tasks that adds an optional delay at the end of the bg-2106
task, causing the scheduler to pause before the next task commences. This can be used to
allow actions that affect the state of the Runtime Resource (such as Login or Log out) to
complete before subsequent actions are performed and avoid errors such as Command not
valid at this time – resource stopping.
A number of database changes have been made to improve performance in the following core bg-2018
areas of Blue Prism: bg-2019
• Work queues - Queries on completed work queues, exception items, and work queue bg-2027
statistics have been optimized. A further improvement in this area reduces the time
bg-2085
taken to retrieve items from a queue based on Item Key filters.
bg-2086
• Schedules - Queries on schedule triggers, schedule log entries, and task sessions have
bg-2087
been optimized.
bg-2021
Control tab.
The default timeout that an Application Server allows a Resource to respond has been bg-2099
increased from 10 to 60 seconds. This reduces the likelihood of Resources incorrectly appearing bg-2081
offline.
received.
An unhandled exception no longer occurs when attempting to capture font details using the bg-2213
BPDiagnostics utility.
Login Agent



Previous Releases
Version 6.3: August 2018

Notices
Login Agent Login Agent has been updated for the 6.3 release.
Important Notices A number of new security mechanisms are introduced with this version – the
upgrade notices must be reviewed before applying this release.
This release includes all of the improvements introduced in 6.2.1.
Certifications


Previous Releases
Enhancements

Multi-team Environments enable organizations to model increasingly complex security ep-56
configurations within Blue Prism by extending the existing role-based access controls to
enable more granular configurations. These capabilities better enable organizations to share
Blue Prism assets, such as Business Objects and Runtime Resources, with multiple teams
within a given Blue Prism environment.
For example, users who are members of a team may have full access to some Business Objects
but may only have the ability to view or execute others, as may be appropriate for assets that
are shared by multiple teams.
Multi-Team Environments introduces the following key highlights to Blue Prism:
• An Access Rights option has been added to the context menu for groups of Processes,
Objects, and Resources from where permissions are applied for the items in that group.
The option is also available for each item in a group, providing a read-only view of the
permissions applied for the group.
• The mechanism provided by this feature for securing access to Resources, replaces the
previous capability of applying permissions directly to individual Resources. Any
previously applied permissions must be manually reconfigured.
• New Default groups have been added for Processes, Objects, and Resources. When
logging in to Blue Prism following an upgrade, all Processes, Objects, and Resources that
were previously stored at the top level in their respective folders, are added to a default
group - items can no longer be stored at the root level in a tree.
• New Execute, Execute as Web Service, and Manage Access Rights permissions have been
introduced and a number of existing permissions have been updated.
For more information about Multi-Team Environments and how to use them, see the v6.3 User
Guide – Multi-Team Environments, available from the Blue Prism portal.
Native support for automating web pages and applications in Chrome is provided within Blue ep-110
Prism through the use of a Blue Prism Chrome extension. This allows Blue Prism to interact
with web pages and applications, presented in Chrome, so that business processes that rely on
applications presented in this browser can easily be modelled.
The Application Modeller wizard has been updated with a new additional Browser-based
Application (Chrome) application mode that enables Chrome elements to be spied and used
within Business Objects.
As part of this feature, the Blue Prism installer has been updated to enable the installation and
removal of the extension.
For more information about the Blue Prism Chrome extension, see the v6.3 Data Sheet - Native
Chrome Integration, available from the Blue Prism portal.
The Blue Prism installer has been updated to provide the optional installation of: us-2612
• The Chrome Browser Automation Extension (via a registry setting) us-2534
• The Outlook interop DLL required if the MS Outlook Email VBO is used

Previous Releases

A number of improvements have been applied which improve the usability of child or nested us-1778
collections: us-1779
• A child collection within a nested collection can be referenced using dot (.) notation.
• A child collection or a value within a child collection can be retrieved or set using dot (.)
notation.
• A child collection can be stored or used directly in a range of scenarios such as:
• Store In addresses (e.g. calc stages, multicalcs, output parameters)
• Collection actions (e.g. Add Row, Copy Rows, Count Columns, Count Rows,
Remove all rows, Remove Row)
• The mechanism of serializing the XML representation of collections has been optimized
to reduce the size of the data transmitted between components. Primarily this benefits
situations where nested collections are in use.
A new Web Service Consumer role has been created to simplify the ability to apply the correct us-2401
permissions to user accounts that will be used to consume Blue Prism Processes and Objects
exposed as Web Services. This role grants the necessary execute permissions without providing
access to areas of the interface, such as Control Room. The role can be used in conjunction
with the capabilities of Multi-Team Environments to restrict which exposed Objects and
Processes can be accessed by user accounts assigned to this role.
A number of session management commands (create, start, delete) no longer work by default. us-2561
They have been superseded by createas, startas, and deleteas which require the use of the
getauthtoken method.
While not recommended, the previous methods can be re-enabled by disabling the new setting
that enforces permissions of controlling users when carrying out session management actions.
When selecting to override the session logging level on the Runtime Resource (via Resource us-1811
Management) it is now possible to select Errors Only logging. When a Runtime Resource is
configured with this override, session logging will be reduced to only log stages which result in
an error being reported.
The status message shown in the Blue Prism client when connected directly to a database has us-2078
been updated. It now presents the reported SQL version number instead of “Unknown” for
situations where the friendly name for the SQL version is not known.
The way that pools and their members are displayed within System > Resource Management us-2152
has been updated so that resources appear under their pool rather than separately.

Previous Releases

A number of improvements have been made to the Session Management pane in Control Room: us-2527
• The session management pane in Control Room has been updated to show the top 5000 bg-1819
records, ordered by start time descending. The maximum number of rows can now be us-2796
selected using the drop-down and the data is refreshed from the database each time a
bg-1927
saved filter is used or the currently loaded dataset is (re-)ordered.
• When saving a Session Management filter, changes are no longer incorrectly applied to
the default Today filter. The behavior where the names of saved filters are lost has also
been improved.
• When first accessing Control Room, the default Session management sort order is now
set to be Start Time descending. Additionally, the Session Management column sorting
is now maintained when returning to Control Room after having navigated away.
When users manually change or set the value of a Session variable via Control Room, the us-2214
action is now recorded with the session log.
It is now possible to alter the process behavior when applying updates to a collection that was bg-1321
copied from an inner, or nested collection. When this optional change is applied, the
relationship between the original and nested collection is affected and is passed by value,
rather than by reference. When the data is passed by value, changes are not reflected in the
original collection. This is implemented on a per process basis and requires a manual update
to the process XML via export and re-import.
For advice on applying this change see the knowledge base article:
How do I update a copy of an inner collection or nested collection, without affecting the
original?
The attribute named Match Index is now available when modelling elements using UI bg-1440
Automation.
The action of manually releasing a lock in System > Workflow > Environment Locks now results bg-1412
in an entry being made into the audit log.
All relevant Blue Prism user interface controls have had their scale mode updated to improve us-1903
the presentation of the interface when installed on Japanese operating systems.
All log messages written to the console window of BPServer.exe are now timestamped to us-2746
improve analysis and troubleshooting.

Previous Releases


A number of security enhancements have been to revalidate actions taken within the Blue us-2150
Prism Client against the user’s permissions on the server (where deployed). This includes:
• Manage (and delete) Exception Types
• Create/Update/Delete Environment Variables
• Create/Update/Delete external Web services
The manage credentials functionality has been updated so that the password and property us-2160
values, which are not required, are no longer included in the underlying data object. This
reduces the likelihood of sensitive information from being discovered. Additionally, the user
interface now clarifies that blank or duplicate property names cannot be used.
Within Credential Manager, the access rights tabs for each credential have been reordered to us-2525
give prominence to the recommended “Security Roles” capabilities. New descriptions on each
of the tabs that allow restrictions by Security Role, Process and Resource have been added to
clarify the nature of the restriction that the respective settings enable.
A number of reconnection issues have been addressed: bg-1438
• Runtime Resources now correctly reconnect following an SQL Server Database restart. bg-1513
An issue introduced in 6.0, meant that when a Resource attempted to reconnect to the bg-1555
database either directly or via an Application Server, an error reported that the Runtime
bg-1350
listener was offline and tried to restart every two minutes even though it was already
online.
• The behavior has been improved when refreshing the view in Control Room if there is an
issue communicating with the database. It now correctly reports the state of the
connection and presents a meaningful error.
• Following an interruption in the connection between a Runtime and the Application
Server, the Runtime Resource reported that it was unable to calculate the run mode of
its sessions. This mechanism has been updated.
• Following an Application Server service restart, scheduled jobs previously failed to run
and required the Run Now feature to manually triggered. This has now been fixed so that
all schedules restart as expected following an Application Server service restart.

Previous Releases

A number of improvements have been made to improve the performance and responsiveness of bg-1740
the platform when version 6.0, 6.1, 6.2 or 6.2.1 is deployed. Primarily, albeit not exclusively, bg-1798
these changes benefit situations where a WCF server connection mode is in use:
bg-1843
• Improvements to the responsiveness of Control Room while the Runtime Resource
us-2599
connectivity status is refreshed. Actions such as moving between Session Management
us-2620
and Schedules, expanding/collapsing the group structure, and dragging a Process onto a
Runtime Resource are improved. us-2623
• Minor improvements to the mechanism used to re-draw the group hierarchical tree us-2630
structure when scrolling. us-2632
• Behavior improvements when navigating quickly across the areas of Blue Prism while us-2656
data is still loading. us-2658
• Optimization of data loading mechanism such as when entering Control Room tab, using us-2678
Session Management, entering Studio tab, and loading a dashboard.
A number of fixes have been applied to Active Queues to address issues experienced in Version bg-1801
6, including: bg-1802
• Queue totals (Worked, Pending and Deferred) not updating as expected. bg-1803
• Incorrect totals of available and busy resources being reported when Resources (or bg-1812
Resource Pools) are offline.
bg-1824
• Exceptions were reported when navigating away from Active Queues while the data is
bg-1846
loading.
bg-1848
• Exceptions were reported when assigning work to a Resource that was recently offline
bg-1849
• Quickly selecting different Active Queues causing the incorrect queue information to be
bg-1850
presented.
bg-1864
An issue that caused Control Room to crash when selecting the Scheduler node if the schedule bg-1304
had more than 2000 log entries, has been addressed.
An issue that prevented screen captures if Preserve the type and detail of the current exception bg-1696
was selected in the exception action, has been addressed so screen captures occur irrespective
of the option to preserve the type.
The following issues have been addressed: bg-128
• Where a stage has been configured with a custom warning threshold value, but the value bg-126
specified was incorrectly interpreted to be seconds instead of minutes. bg-1804
• Where the Resource Pane in Control Room incorrectly reported that a Runtime was in a
warning state even though it was had subsequently moved on and cleared the warning.
Previously, to reset the Resource Pane, the user was required to navigate away from
Control Room.
• The Resource incorrectly reported a process to be in a warning state when a certain
server connection error was experienced.
An intermittent issue that resulted in extended login times in environments with large numbers bg-1891
of Runtime Resources has been addressed.

Previous Releases

An improvement has been made to address the issue where, after cloning a published process bg-1847
using Save As, if the user selects to publish the process, this is not saved until the new process
is closed and reopened.
An issue has been addressed whereby the action of encrypting or decrypting a data using an bg-1628
encryption scheme incorrectly required full Credential Management privileges. The mechanism
used for these actions now applies the correct permissions, which improves the behavior when
using the Blue Prism Encryption VBO to encrypt and decrypt data.
The messages presented when carrying out an import of a release have been clarified to bg-1326
address an issue where, in some situations, when a user selected not to import a Business
Object or Process because it already exists, they were informed that it had been imported.
An improvement has been applied that addresses a scenario where pressing enter when a bg-581
group or folder was selected resulted in unexpected behavior.
It is no longer possible to rename a group to have the same name as another group at the same bg-630
level in the hierarchy. This addresses the scenario where a group with a duplicate name, at the
same level in the hierarchy, would be hidden from view.
This affects groups of queues, processes, objects, tiles, users, and resources.
The scenario where an unexpected error was presented when deleting a Process that had not bg-424
been run, but for which Process Alerts had been configured, has been addressed.
An issue has been fixed to address scenarios where Process Alert users incorrectly received the bg-771
message Alert Received but cannot be displayed, because this machine is not registered.
The Export current view as report option in Control > Queue Management is no longer available bg-536
if there are no queues in the Queue Contents section of the screen. Previously, the option was
available and would produce and error as no queues were available.
Runtime Resources now restart as expected from the Resources system tray context menu bg-705
when the restart action is selected and when instructed using the /resourcepc switch.
Previously, an unhandled exception was generated.
An improvement to the session log viewing functionality has been applied to ensure bg-940
meaningful information arising from errors is not hidden.
The scenario where an unhandled exception is thrown when the scheduler attempts to start bg-1134
sessions across multiple Runtime Resources if one or more of the Runtime Resources is offline
has been addressed.
The following improvements/fixes have been applied when using WCF server connection bg-1109
modes: bg-1482
• An improvement to the serialization mechanism that is used for transmitting a collection bg-1630
over a WCF connection has been made to better cater for large collections.
• The data packets generated when creating or updating schedules over a WCF server
connection have been optimized to improve performance and reduce the potential for
SQL timeouts.
• An issue has been addressed that resulted in an error occurring when renaming a group if
using a WCF connection
A redundant server method SetLoggedInMachine has been removed to prevent it being us-2529
exploited by a malicious actor.

Previous Releases

An update has been made to reduce the occurrence of an error that reports that the machine bg-1753
name parameter has been set to null.
When parsing XML from an HTTP response, a static encoding format was used resulting in bg-1166
scenarios where responses that contained multi-byte characters produced an error. The
encoding format specified in the SOAP HTTP response is now used when consuming third-
party web services.
A usability improvement has been made within region editor. Users are now directed to first bg-1627
select a Location Method, and in situations where the Coordinates options is selected, the
incompatible Position option named Anywhere is no longer available.
An issue has been addressed whereby an error was encountered when attempting to use Check bg-1188
JAB Attribute condition in a Wait stage while automating a Java application. The data type set
in the condition now uses the correct letter case and the Wait stage no longer produces errors.
In Audit > Design > Control, the automatic validation settings when opening, resetting, and bg-1221
saving processes were not applied when using the X button to close Process or Object Studio.
With the appropriate settings applied, the Save button correctly allowed unvalidated changes
to be saved but pressing the X button carried out unexpected validation and prevented the
window from closing.
The close button now matches the behavior of the Save button with respect to observing the
validation settings.
Adding or removing a breakpoint within the definition of a Business Object or Process is now a bg-1309
recognized change and users are prompted to save changes when exiting the designer.
Validation has been added that displays an error when an invalid Data stage is referenced as an bg-1289
element parameter in a Wait stage. Previously, the error would only be highlighted when the
stage was executed.
The RemoveRow action has been updated to correctly iterate through the rows when removing bg-1283
duplicates. The previous mechanism caused items to be skipped during processing as the loop
stage did not update correctly.
When using Active Accessibility, it is now possible to select any item from a combo box drop- bg-1315
down list, irrespective of whether the item is currently visible due to being presented within a
scroll list. Prior to this fix, if scrolling through the drop-down was required to locate an item,
an error occurred.
A small number of incorrect hard coded database schema references within the upgrade scripts bg-1327
have been removed to address an issue where the database upgrade may fail on deployments
which do not use the default dbo schema. These references were incorrectly introduced in the
6.2 upgrade scripts. For scenarios where the default schema was not used but the upgrade
succeeded, the incorrectly specified schemas are addressed by this fix.
A stored procedure (usp_addPermission) that incorrectly remained in the database following an bg-1719
upgrade has been removed.
When configuring a connection to the Blue Prism SQL Server database, it is now possible to bg-1383
specify parameters that include special characters such as + $ and ‘. When configuring a
connection that uses SQL authentication, this enables use of these characters within the
password.

Previous Releases

An issue has been addressed where copying a group (using CTRL + drag) caused an error when bg-1157
the client was connected to the database via an Application Server.
The encryption scheme settings applied to a queue are no longer impacted if the queue is bg-1676
overwritten when importing a release.
An issue has been addressed where sessions that took place on debug Runtime Resource (i.e. bg-1511
one started automatically when logging into the client) incorrectly recorded the session end
time in British Standard Time (BST).
Processes accessed using the View selected process option from a different Object or Process bg-1111
are now correctly read-only. Previously, a scenario existed where a user attempting to add an
item to a collection within the process would be presented with an error.
An issue has been addressed for scenarios where an error occurs when closing the Application bg-1301
Modeller while a spy-mode is active, i.e. the user has selected to use a spy-mode and
subsequently shuts the Application Modeller without selecting an element.
An issue has been addressed where it was possible to make changes to the permissions bg-1305
associated with the following system roles: System Administrator, Runtime Resource.
The AutomateC run method has been updated to support the new system settings that validate us-2792
the calling user when carrying out session management actions.
An issue has been addressed where the AutomateC.exe export queue action incorrectly clears bg-1663
all completed work items if a queue is specified, but the specified queue contains no
completed items. The behavior of clearing all completed queue items should only occur if no
queue is specified.
When making changes to previously configured Startup Parameters within Control Room, bg-1667
pressing Cancel incorrectly resulted in the changes being saved. This issue has been fixed and
pressing Cancel correctly disregards any changes.
View-only (read-only) mode of the Object or Process designer correctly prevented any changes bg-1218
from being saved. It has now been updated to prevent changes from being made to the process
flow when using View-only mode to avoid a situation where users believe they are making
changes that will be saved.
The Process/Object validation logic has been updated to correctly present an error when a bg-1516
reference to an action is present, but the action has been deleted.
The pools management screen has been updated to correctly reflect whether a resource within bg-1600
a pool has been retired.
The API Documentation help option is now only available once a user has authenticated with bg-1946
the environment. This addresses an issue where an error was presented because the items
within the environment could not be queried prior to the login taking place.

Previous Releases

A number of improvements or fixes have been applied when Exposing Blue Prism Objects or bg-1706
Processes as Web Services: bg-1709
• An issue has been addressed whereby malformed requests to a Blue Prism Object or bg-1865
Process, exposed as a web service, would return an error and result in no further Web
Service requests from being processed.
• Exposed Blue Prism Web Services no longer apply case sensitive logic when processing
headers.
• An issue has been addressed where no response was provided if authentication failed
due to invalid credentials – a credentials error is now provided.
The mechanism that presents error messages in situations where a connection to the server bg-1685
cannot be established has been improved so that where error messages are available, they are
now presented to the user.
The list of third party webservices available within the System area is now presented using a bg-533
different user interface control. This removes the ability to inadvertently disable all Web
Services when accidently highlighting multiple rows.
The following changes have been applied: bg-1534
• The description of the Local parameter of the MakeDateTime method has been updated. bg-1618
• The description of the Queue name parameter of the Work Queues, Get Next Item has
been updated.
In the Application Modeller wizard, an option has been renamed from Restrict to non-invasive bg-1200
techniques to Disable invasive techniques (hooking).
The XML that is produced when exporting an Object or Process that featured a single row bg-1479
collection has been updated so the <singlerow/> attribute is no longer duplicated.
The Choice stage form has been updated to improve the scaling behavior when resizing. bg-1415
The mechanism used to transport exceptions to the server that are raised on the client using a bg-1910
WCF connection has been improved.
A fix has been applied to correct the capitalization of messages presented while validating or bg-1234
stepping through a process or object.
The icon presented as part of the loading graphic has been updated us-1779

Previous Releases
Login Agent
The mechanism used to create the named pipe to the Credential Provider has been improved us-2665
to better cater for scenarios where Logout and Login actions occur within quick succession.
When logging is enabled, the status and sub-status are now captured to enable additional us-2196
diagnostics.
When the Login Agent encounters invalid commands, details of those commands are now bg-1547
logged.


A number of Visual Business Objects (VBOs) are provided in the Blue Prism release - new or updated VBOs
are listed below. Changes within VBOs are only applied when a VBO is explicitly imported into the
environment.
behavior.
Utility - JSON
A new action called JSON to Collection (skipping JArray) has been added that simplifies the us-1782
structure of the returned collection if the JSON contains a property which is an array of
objects. The original JSON to Collection action remains available for use.

A new MS Outlook Email VBO is now available that provides a number of actions for us-2192
processing emails within Outlook such as sending, deleting, retrieving, and saving emails and
attachments.
The VBO has been validated against Outlook 2016 and requires each device where it operates
to be configured with a Microsoft Outlook Interop DLL within the Blue Prism installation
directory.
The Blue Prism installer has been updated to optionally place the DLL in the correct location.

Previous Releases
Version 6.2.2: October 2018

Notices
the same functionality as the version provided with Blue Prism 5.0.33.
Important Notices This is a patch release of 6.2 and is built on version 6.2.1. Once installed,
deployments featuring this version can only be upgraded to version 6.4 or above,
once available.
Upgrades to versions earlier than 6.4 are not supported.
Certifications


Previous Releases


A new setting has been added to scheduled tasks that adds an optional delay at the end of the bg-2106
task, causing the scheduler to pause before the next task commences. This can be used allow
actions that affect the state of the Runtime Resource (such as Login or Log out) to complete
before subsequent actions are performed, and avoid errors such as Command not valid at this
time – resource stopping.
A number of database changes have been made to improve performance in the following core bg-2018
areas of Blue Prism: bg-2019
• Work queues - Queries on completed work queues, exception items, and work queue bg-2021
statistics have been optimized. A further improvement in this area reduces the time
bg-2027
taken to retrieve items from a queue based on Item Key filters.
bg-2085
• Schedules - Queries on schedule triggers, schedule log entries, and task sessions have
bg-2086
been optimized.
bg-2087
Control tab.
The default timeout that an Application Server allows a Resource to respond has been bg-2099
increased from 10 to 60 seconds. This reduces the likelihood of Resources incorrectly appearing bg-2081
offline.
received.
Login Agent



Previous Releases
Version 6.2.1: May 2018

Notices
Important Notices This patch release is built on version 6.2 of Blue Prism and forms a valid upgrade
path to future production releases.
Certifications



A fix has been applied whereby, following an Application Server service restart, scheduled jobs bg-1350
failed to run. If the schedule was restarted manually using the Run Now feature, the scheduler
reinitializes. This has now been fixed so that all schedules restart as expected.
A schedule configured to run a number of tasks in sequence was attempting to start all tasks bg-1134
simultaneously, resulting in a KeyNotFoundException. This error is now prevented and the
schedule executes jobs correctly.
An issue that may have caused an upgrade failure if the default dbo schema was not used in bg-1327
the database has been addressed by removing hard-coded references to this schema within the
6.2 database scripts. This issue only affected environments created using or being upgraded to
version 6.2. Database objects, incorrectly created with a dbo schema when upgrading to 6.2,
will be automatically updated to use the appropriate schema when applying a database script
containing this fix.
When carrying out a database upgrade, the error reporting has been improved to provide bg-1337
greater visibility of the specific change that is presenting the issue.
A fix has been implemented to address a prolonged connectivity issue between the Resource bg-1592
and the Application Server which caused the Resource to stop attempting to re-establish the
connection. This made it unavailable within the Blue Prism environment until the Runtime
Resource is restarted.

Previous Releases

A fix has been applied so that Runtime Resources correctly reconnect following a SQL Server bg-1438
Database restart. Previously, an issue introduced in 6.0, meant that when a Resource attempted
to reconnect to the database either directly or via an Application Server, an error reported that
the listener was offline and tried to restart every two minutes even though it was already
online.
The following improvements have been made to WCF connectivity: bg-1482
• The data packets generated when creating or updating schedules over a WCF server bg-1555
connection have been optimized to improve performance and reduce the potential for
SQL timeouts.
• An update to the re-connection mechanism has been applied to cater for situations
where, following an interruption in the connection between a Runtime and the
Application Server, the Runtime reported that it was unable to calculate the run mode of
certain processes.
An issue that was preventing some Resources reconnecting following a network outage on the bg-1598
Application Server has been fixed. The Resources failed to authenticate and log in after a
network outage of 90 seconds or more between the Resources and the Application when using
Blue Prism native authentication. The following error was produced on affected resources:
Failed to shutdown Login Agent Resource on Port:0
Unauthorized: User not logged in
It is now possible to select the parent region when using a relative search mode with a bg-1556
coordinate-based region.
It is now possible to alter the process behavior when applying updates to a collection that was bg-1321
copied from an inner, or nested collection. This optional change affects the relationship
between the original and nested collection as data is passed by value, rather than by reference,
so that changes are not reflected in the original collection. This is implemented on a per
process basis and requires a manual update to the process XML, via export and re-import.
For advice on applying this change, see the associated Knowledge Base article.
When using Active Accessibility, it is now possible to select any item from a combo box drop- bg-1315
down list irrespective of whether the item is not currently visible due to being presented
within a scroll list. Prior to this fix, if scrolling through the drop-down was required to locate
an item, an error occurred.
The attribute named Match Index is now available when modelling UI elements using UI bg-1440
Automation Navigator. This aligns it in line with other spy modes that provide this option.

Previous Releases
Login Agent


A number of Visual Business Objects (VBOs) are provided in the Blue Prism release but changes are only
applied when a specific VBO is explicitly imported.
behavior.
Object - MS Excel VBO

This VBO was added in error in 6.2 and has now been removed. The functionality provided in bg-1310
this VBO duplicated that of the Object - MS Excel.
Object - MS Excel
The help text for this VBO has been updated to clarify appropriate use of the Show action with bg-1310
Office 2013 & 2016.

Previous Releases
Version 6.2: February 2018

Notices
Database Changes This release requires the Blue Prism database to be version 233
Certifications

Enhancements

This version of Blue Prism has been certified for use with the Office 2016 editions of Excel and us-1334
Word. At the time of release, Office 2016 is the version that is provided as a local install when us-1335
using Office 365.
Native support for UIA has been introduced with the addition of a dedicated Spy Mode and ep-19
Application Navigator which can be used when creating application models in Object Studio.
The UIA Application Navigator offers three tree-view displays of the automation elements
available within the target application, in descending order of detail presented on screen: Raw,
Control and Content.
• Raw displays the full tree of automation elements which closely follows the native
programmatic structure of an application. This is the most detailed view available
• Control displays elements which show information to the user or enable the user to
perform an action.
• Content contains elements which convey information in a user interface, including UI
elements that can receive keyboard focus.
UIA offers improvements in speed, accuracy and resilience over Active Accessibility (AA) when
creating automations. AA remains as supported spy-mode.
It is now possible to import Releases via the command line. Releases that are imported us-1505
programmatically will use pre-configured defaults to resolve environment import conflicts.
This functionality is intended for use by advanced Blue Prism users.

Previous Releases

The automation design validation can now be set to warn or error if a Process or Object us-1194
contains an exception type that has not previously been used in the environment. This
provides an elevated ability to ensure that only pre-determined exception types can be used.
When using this functionality, the following points need to be considered:
• The list of exceptions currently in use in the environment is only generated once the
Scan Business Objects action (or Scan Processes) has been performed.
• Exception types now used or imported in Objects and Process are automatically added
to the validated list of permitted exceptions.
A new capability is provided to release database locks which can occur during archiving. The us-909
lock can be released by selecting 'Release Archive Lock' from the Archiving screen within the
System panel. Once selected, the lock is cleared from the database and an audit entry is
created.
When a Resource first initializes, if an archive lock is in place, the Resource will automatically
attempt to clear it.
Users with the Security - Manage Credentials permission can now create and update us-1663
credentials using two additional AutomateC command line actions - /createcredential and
/updatecredential. By default, new credentials will be created with 'all processes', 'all
resources' and 'all security roles' permissions. The values of existing credential properties can
also be set and updated by using a /setcredentialproperty action.
A number of options have been introduced when exposing Processes and Objects as web us-1499
services: us-1350
• Document/literal encoding can now be enforced when exposing a web service in the bg-1034
user-interface and also via the command line with a /forcedoclitencoding switch. This
will force all actions (including Initialize and Cleanup) to use the specified format. If this
enforcement is not selected, the Initialize and Cleanup actions will use RPC encoding,
and the encoding for custom actions will be determined based on whether a collection
data type is defined as an input or output parameter.
• The web service address location that will be displayed within the WSDL of the service
can now be optionally configured with an override address. This option is configured
through use of the /wslocationprefix command line switch when starting a Runtime
Resource. If no location is set, the Resource will continue to be addressed either by the
machine (short) name or FQDN as configured under System Settings. The web service
address location of a Resource can now be specified via an optional /wslocationprefix
command line switch. If no location is set, the Resource will continue to be addressed
either by the machine (short) name or FQDN.
• When calling a Process or Object which has been exposed as a web service, outputs that
are simple types no longer have an empty XML namespace (xmlns=""). For backwards
compatibility, users can specify that a Processes or Object using RPC encoding should
continue to use legacy name spacing when first exposing the Process or Object.

Previous Releases

It is now possible to specify that a Runtime Resource should not start a HTTP end-point by us-1500
applying an additional /nohttp switch to a /resourcepc command. This option should only be
used where the Resource is not required to expose any Web Services and does not need to be
controlled via the HTTP interface. Once set, HTTP requests to the resource will not get a valid
HTTP response.
An additional dashboard tile has been provided (License Information) which measures and us-1491
displays license entitlement vs usage for Concurrent Sessions, Published Processes and
Resources. Only data relevant to the deployment license is displayed.
The Runtime Resource HTTP End-point logging capability primarily provided to support Splunk us-1480
integration has been expanded to allow basic HTTP authentication. This is in addition to
token-based authentication.
Downloading or exporting Audit or Session logs now results in an Audit Log entry. us-1063
us-1064


The responsiveness of several screens and controls has been improved when there are many us-1608
Objects or Processes present within an environment, such as when opening an Object or
Process within the designer or interacting with the tree-view in Process/Object Studio. A new
loading modal has also been introduced.
The maximum execution speed in Process/Object Studio has been increased to make to us-807
execution speeds comparable to Control Room. As part of this change, stages are no longer
highlighted when Objects and Processes are run at maximum speed.
The Runtime Resource start-up procedure now ignores invalid characters within the SSLCert bg-971
value to address issues whereby copying the thumbprint from the Certificates Store resulted in
certificate errors being reported within Blue Prism. Where invalid characters are found, a
warning will be written to the event logs on the local device.
Blue Prism licenses are now unloaded from memory when the user account is signed out of the bg-1073
Interactive Client. This resolves an issue whereby switching between environments causes the
environment to report an incorrect license allocation to that user.
An infinite loop no longer occurs when a schedule has been configured with an execution bg-440
interval greater than the available window of operation.
Calendars with no working days defined no longer generate an infinite loop when determining bg-1150
the next scheduled execution time.
An issue has been addressed whereby the import of large releases containing calendars and bg-1042
schedules over an Application Server connection would fail.
The Unlocking Wizard can now be used to successfully unlock failed Processes over an bg-1168
Application Server connection that uses a WCF connection mode.
From and To entries in Audit Logs now display correctly and are converted from UTC to Local bg-1174
time when displayed in the Audit Log viewer (which displays information in the viewing users
Local time). This addresses an issue whereby log entries would be incorrectly displayed across
different days when viewed in the Audit Log viewer.

Previous Releases

The Blue Prism installer now correctly checks that .NET 4.7 has been installed on the device us-1689
before proceeding.
Image Regions are now successfully detected at run-time even if the top and bottom padding bg-1020
of the image location has been set to 0. Previously, the region would not be successfully
located unless the padding was set to a value greater than 0.
List Regions can now be utilized with the Relative Positioning location search method in bg-1019
Region Editor when creating process automations with Surface Automation techniques.
Element match values are now limited at 32,000 characters, this prevents UI crashes when bg-1084
using the Active Accessibility spy-mode to capture application elements.
It is no longer possible to assign a retired Resource to a credential. Retired resources are still bg-1179
visible when editing credentials to which they are currently associated.
Schedule startup parameters can now only be created and edited by users with the bg-947
corresponding Create and Edit Schedule permissions.
An issue where using the List View to view Session Logs caused the data to be displayed bg-1027
incorrectly has been addressed.
Group names are now ignored when looking up an Object in the group structure by name. bg-1071
Prior to this change, Processes/Objects calling an Object with the same name as the group it
was part of would display a Missing Action error in the Action drop-down.
Processes exposed as Web Services are no longer hidden when configuring Process Alerts. bg-1196

Previous Releases
Login Agent


behavior.
Object – MS Excel
The VBO has been certified for us with the Office 2016 Edition of Excel. -
Object – MS Word
The VBO has been certified for us with the Office 2016 Edition of Word. -
Utility – JSON
A compiler error message is no longer presented when editing the VBO. bg-1056
Utility – Split Collection

An issue has been resolved whereby the Split Collection Action was not able to successfully bg-1096
split the data from one column of the source collection into multiple target collections.

Previous Releases
Version 6.1: October 2017

Notices
Important Notices This version requires all Blue Prism devices to be configured with .NET
Framework 4.7.
The information and guidance provided under the heading Upgrading from
Versions prior to 6.0 must be reviewed as part of the upgrade procedure. This
version is built on 6.0.
Certifications


Previous Releases
Enhancements

This version of Blue Prism has been certified by Veracode as PCI DSS Version 3.2 compliant in
sections 6.1, 6.3.2, 6.5, 6.6, and 11.3.2 and PCI PA-DSS Version 3.2 Sections 5.1.4, 5.2, 7.1.1,
7.1.2, and 7.1.3.
Runtime Resources that secure inbound connections are now configured to use TLS 1.2 by us-1191
default, this includes instructional and web service connections in addition to outbound
HTTPS connections.
Session log data for external consumption introduced in 6.0 is now directed to a new event log us-1151
- BP Analytics. This enables analytics from multiple services on the same machine to be
differentiated by using the event source. Event sources are created for each server config in the
format BP Analytics Service - {server config name}.
A number of updates have been made to the audit codes used by Blue Prism when recording us-1018
audit events: us-1021
• Release Manager audit events now use a code prefix of E. Previously, Release Manager
events shared the code prefix of R with Resource events.
• Scheduler audit event codes now increment using 4 digits, rather than 5, which makes
them consistent with other audit event code patterns.
A new MainframeSendKey capability is provided within a Navigate stage of new Business us-1274
Objects associated with an Application Model configured to use a HLLAPI or .NET API bg-293
mainframe connection. This provides a new mechanism for sending ASCII text and control
characters such as {enter}. The help has been updated to provide additional information.
A new option named Generate Support Information has been added to the BPDiagnostics us-1272
utility that will allow an elevated user to manually generate a package of diagnostic
information within a zip file.
The zip file contains information about the configuration of Blue Prism and associated utilities
on the local machine such as:
• Blue Prism installation and configuration information (including Login Agent and
MAPIEx)
• Operating system and local security setting configuration
• Applications installed and running on the device
• Networking configuration
• Event logs
Release manager now supports the inclusion of the newly introduced Published Dashboards us-1188
within a release package to allow the porting of these between environments. It is necessary
for users who wish to import a Published Dashboard to be granted the Import Published
Dashboard permission. Users who have the Import Global Dashboard role at the time the
update is applied with be auto-granted this new role.

Previous Releases

The following of fixes and minor improvements are introduced with this version.

Several improvements have been made to the UI when using the Interactive Client with a bg-911
Japanese locale. Issues which have been addressed include: bg-915
• An over-extended label which previously prevented use of the Number of Attempts at bg-916
Writing a Log Entry in Logging Options field under Process Information. bg-918
• The Control Room UI not being displayed correctly when re-sizing the screen.
• The edit user form re-type password value being incorrectly unpopulated.
• Layout of the start and end stage forms to appropriately present the intended fields.
The Collect Utilization and Productivity Statistic setting can now be enabled and disabled bg-815
without having to restart the Application Server for the setting to take effect.
The default Encryption Scheme method is now set to AES-256 AesCryptoService when bg-908
configuring a new Encryption Scheme via the Server Configuration utility and the Interactive
Client.
This aligns with the default setting applied when using command line options.
The mechanism used to load groups into the Resources-Management and Workflow-Queues us-1179
tree-views in System Manager has been made more performant when handling large numbers
of records.
Importing a release now occurs as a background operation to improve performance and bg-950
provide a progress indication when importing over a WCF connection
The background calculation process for determining the next run time of a schedule in the bg-944
Scheduler has been made more efficient. This primarily affects scenarios where there is a large bg-826
volume of schedules set to run concurrently.
The region mode searching logic has been updated to prevent a memory bg-1011
AccessViolationExeption being presented when using searching for a region that is configured
with a position type of relative. The error was presented when the location of the parent region
was such that the expected position of the associated child region is outside of the acceptable
search area.
The 64-bit installer has been updated to address a dependency issue that affected the us-1251
managedspylib functionality and prevented it from loading.
Auto-archiving has been updated to automatically delete orphaned sessions to reduce the bg-529
likelihood of a Specified Cast is not Valid exception being presented that indicated that users
need to manually delete these records (BPASession records where statusid=6) prior to using
archiving functionality.
Blank lines in the results of the capabilities (caps) command no longer results in an exception bg-909
being presented.
Runtime Resources which have been configured to be private are now only controllable by the bg-907
allocated user when using telnet.
Additionally, the telnet capabilities (caps) command has been restricted such that it is only
available to authenticated users.

Previous Releases

An issue introduced in 6.0 whereby session logs were not generated by an executing process if bg-951
that process featured a sub-process has been addressed. The action of the sub-process exiting
and returning the parent process caused the session logs to stop being capture.
An issue has been addressed whereby Blue Prism would crash when trying to launch or attach bg-876
to the RUMBA mainframe emulator application.
Changing the name of a user in Active Directory no longer results in an unhandled exception bg-906
when refreshing the user list in Security - Users.
An issue has been addressed whereby passwords were being submitted using an incorrect bg-834
format to Java applications when using a Write Stage to write a password from a data item set
as Text.
Users signing out of the Blue Prism Client when process alerts are configured will no longer bg-828
receive an error if they select to allow alerts to continue to be received.
The logic used to ensure that there is always a system administrator account defined in an bg-963
environment configured to use Blue Prism native authentication has been updated to address a
scenario where the action of deleting a non-system admin user was incorrectly prevented.
An update has been made to the designer validation logic so that adding an un-configured bg-967
Navigate stage no longer results in an error being reported.
An error is no longer presented upon disconnection from the AttachMate Extra emulator. bg-974
The mechanism used to determine the application directory has been updated to be based on bg-1015
a library rather than an executable.
Login Agent


Previous Releases

behavior.
Object - MS Excel
The input parameter used for the workbook name for the Is Read Only action is now set to a bg-895
Text datatype rather than Number. This avoids the error which occurred previously when using bg-864
the action.
The Save Workbook action has been updated to address an issue which resulted in dates being bg-978
saved in the format MM/DD/YY. Dates are now saved in the locale specific format of the system
being used.
The mechanism used when Excel is instructed to exit has been updated to address a scenario bg-995
where Excel is slow to fully exit.
Utility - File Management

Previously, the Get Files Action retrieved the Created, Last Accessed and Last Written entry of bg-846
each file in UTC. The entries were then handled as Local datetimes and converted to UTC when
outputted as part of a Collection.
The DateTime mode of columns containing datetimes are now set to UTC and outputted as
UTC.
This change is now reflected within the v6 Data Sheet – Date and Time Handling.
Utility - Strings
Redundant columns are no longer added in the output when using the ParseCSV action which bg-900
improves performance.

Previous Releases
Version 6.0: September 2017

Notices
Important Notices This version requires all Blue Prism devices to be configured with .NET
Framework 4.7.
The information and guidance provided under the heading Upgrading from
Versions prior to 6.0 must be reviewed as part of the upgrade procedure. This
version is built on 5.0.33.
Certifications

Enhancements
A number of new features and enhancements are introduced in this version of Blue Prism.
Enhanced Surface Automation
Surface Automation techniques have been extended and enhanced to simplify the building of resilient
processes when using Blue Prism Surface Automation techniques to interact with applications.
Optimizations are also provided that improve the performance of these processes as they execute.
Region Editor
The mechanism for defining how to locate regions has been extended. It is now possible to:
• Easily select whether the region should be found based on coordinates or an image match.
• Select the search area for a given region (e.g. anywhere on the screen, fixed position, or relative
position to another region).
• When using image matching and a fixed position, a search area around the position can be defined to
cater for situations where the image may be out of position within a defined tolerance.
• When using relative positioning, the run-time search area for the region will be dynamically adjusted
based on the actual location of the parent item(s).
• Set an RGB color tolerance range for image regions. This allows for variance in the RGB values of the
image pixel colors at run time.
• Create a grey-scale comparison of an image region. This improves the resilience of region detection
when an RGB color tolerance alone cannot be relied upon.

Previous Releases
Process Development
Process studio includes improvements to reduce the complexity when building resilient processes:
• A new check exists condition can be used in Wait stages to check that an image region is present
before continuing.
• An interval can be set between actions within a navigate stage.
• An interval can be set between individual keystrokes in Send and Press Key actions within a Navigate
Stage. (Global Send Keys, Global Send Key Events, Window Press Keys, Window Press Keys with ALT).
Improved Control Room
A number of improvements have been made which provide greater visibility and ease of management of the
workforce. These improvements include:
• The Session Management pane now provides multi-select filters for Processes and Resources, and
subject to being enabled, the session management pane is now auto-filtered based on user selections
in the Processes and Resources panes.
• It is now possible to set a maximum time that a process can spend on a given stage before entering a
warning state. The warning is configured on a system-wide basis with the option to define an override
value per stage.
• The latest stage that was started in a process (along with the start date and time) is now clearly
indicated within session management.
• Navigating away from the Control Room no longer causes the selected resource session view to be
reset.
• A more prominent indication of which resource is the current Resource Pool controller.
• The Workforce Availability tile has been updated to more accurately reflect the status of all resources,
including data on how many are logged out, working, idle, missing and offline.
The Resources panel in the Control Room now contains more detailed information about each Runtime
Resource. The changes include:
• A new mechanism for displaying the state of the Resource such as whether the runtime is idle,
running, offline, missing; as well as the number of sessions that are running on each device. This is
derived based on Runtime Resources proactively providing relevant information on a regular basis.
• Resources which are unexpectedly offline are now shows as missing, and the total time that has
elapsed since the last successful connection is displayed with an upper limit of 5 minutes.
• If a Resource has been set to Private, the user account which to which it is assigned is displayed.
• The connection state information that indicates whether a direct (instructional) connection can be
established from the control room to a given Runtime Resource is now within the right-hand columns
in the pane.

Previous Releases
Windows Communication Foundation (WCF)

The connection modes available when configuring a Blue Prism Server; and when configuring a Blue Prism
client to connect via a Blue Prism Server have been extended to offer Windows Communication Foundation
(WCF) options in addition to .NET Remoting. This offers increased control over the encryption that is applied
to the communication channel.
The new options include:
• WCF: SOAP with Message Encryption & Windows Authentication
• WCF: SOAP with Transport Encryption & Windows Authentication
• WCF: SOAP with Transport Encryption
• WCF: Insecure
This work includes additional command line configurability for setting the connection mode through use of
the /connectionmode switch.
Analytics
Session logs and configurable metric information can now be directed to external systems for cross-
environment monitoring purposes. To accommodate this new functionality, the following changes have been
made:
• The Dashboard tab has been renamed to Analytics. The corresponding user permission group
nomenclature has also been changed to Analytics.
• A new concept of Published Dashboards has been provided. Tiles added to published dashboards will
be periodically executed behind the scenes on appropriately configured Blue Prism Servers and the
results will be logged into the local event logs on those devices.
• A new Design Published Dashboard permission has been provided. This restricts whether users can
create and edit Published Dashboards. System Administrators and users with the existing Design
Global Dashboards permission are granted this permission automatically.
• A new Application Server config setting Enable Published Dashboards is provided. When enabled, the
server will periodically retrieve data associated with the tiles on each Published Dashboard and write
the information to the Windows event log in JSON format for consumption by external applications.
The tile with the longest refresh interval will be used to determine whether or not to refresh all the
tiles on the dashboard and output their results to the log.
Exception Screen Capture
Exception stages can now be configured to automatically save a screen capture of the Resource. The screen
capture is saved with the date and time of the exception, the name of the Resource which took the capture
and the process or object in which it occurred. When using this feature, the following points should be
considered:
• The functionality is enabled/disabled via a system-wide setting.
• Screen captures can only be viewed by users with the appropriate permission.
• The screen capture functionality requires that a default encryption scheme has been configured and is
valid. Only the latest screen capture per Runtime Resource will be stored.
Multi-Lingual UI
Key areas of the user-interface can now be displayed in Japanese when the client is run on a machine with a
Japanese locale.

Previous Releases
.NET 4.7
The platform is now configured to natively use .NET Framework 4.7. This will require all devices where Blue
Prism is to be installed to be configured with this version of the .NET Framework. Additionally, this provides
support for using features of this framework when developing Blue Prism code stages.

Previous Releases
Server Configuration
Several changes have been made to the Blue Prism Server configuration interface to improve usability:
• When configuring a server service, if a valid Windows Service has not already been configured, the user
is alerted via the configuration interface.
• If a Windows Service had not previously been configured for a server profile, the user is given the
option of using an on-screen Create Service button.
• When creating a server profile, the configuration utility now detects if a duplicate name is already
configured.
• The sever profile named Default cannot be renamed or deleted.
• It is no longer necessary to use the save configuration button on the configuration home screen to
save the changes which have been made.
• Server event log options are now grouped under a dedicated Logging tab.
• If the server service is configured as a WCF endpoint, an alert is presented if the service logon on
account does not have the appropriate permissions. Functionality is provided that allows an
administrator to add the logon account to the appropriate access control list (ACL).
• An interface is provided for associating a locally installed certificate with the Blue Prism server service
for scenarios where a WCF connection mode with transport encryption is selected.
Server Deployment
• The Blue Prism Server service now operates as a 64-bit process when deployed on a supported 64-bit
operating system.
• When using the AutomateC /serverconfig command to set up a new server deployment, the encryption
scheme which is automatically created is now labelled 'Default Encryption Scheme'. Previously, the
scheme was labelled 'Credentials Key' by default.
Mainframe Emulators
Support for interactions with mainframe emulators in multiple locales has been extended. The following
changes have been introduced:
• When using the Generic HLLAPI connector, it is now necessary to select the API code page that the
emulator is configured to use. This enables interactions with emulators configured to use a wide range
of locales, including those which contain double-byte character sets. Existing processes will default to
the ASCII encoding translator.
• Interactions with mainframe emulators which display text in a Right to Left (RTL) order has been
enhanced with the introduction of an RTL spying option. When enabled, the location of the spied
elements will be calculated based on the target RTL display.
Tesseract Optical Character Recognition
Tesseract V 4.0 is now installed with Blue Prism. Language packs from previous versions will no longer work
and new language packs must be installed. Directions on how to complete this step are provided in the
product Help.

Previous Releases

A number of fixes and minor improvements are introduced with this version.

This version of Blue Prism is certified Veracode Level 4 and is OWASP security compliant. us-1050
When passing a Collection back from a Code Stage, if the DateTimeMode property had not been us-867
specified, the DateTime objects were being treated as being local time and subsequently being bg-610
converted to UTC. By default, DateTimes that do not have a specified DateTimeMode property
will now be set to UTC when passing a Collection to a Code Stage. This prevents unexpected
time zone conversion.
Session logs are now saved and viewed using the local time of the resource, and not the local us-879
time of the database server. When viewing the logs, a tool-tip translates the resource local time us-999
to the viewing user local time and also provides a UTC offset. The Session Management
overview in Control Room is presented in the Local time of the viewing user.
The message presented when the context under which a Runtime Resource is started does not bg-755
have access to the private key of a configured certificate has been updated to be more
meaningful. This benefits situations where the Runtime Resources are started using the /sslcert
switch but where the user has not been explicitly granted permissions to the private key.
A number of changes have been made to ensure that in environments configured using Blue bg-354
Prism Native authentication, the last System Administrator user cannot be deleted. It is no
longer possible to delete any user that currently has a System Administrator role; and it is no
longer possible to remove the System Administrator role from a user if this would leave the
system without an active user with these rights.
Any Runtime Resource error messages that were previously displayed in a pop-up window are bg-548
now re-directed to the event log when not running in interactive mode. This primarily applies
to Runtimes started by Login Agent prior to being logged in.
Resource pools can now delegate work to pool members when used in an Active Directory bg-745
environment. This issue was introduced when changes were made to how anonymous
resources were authenticated in v5.0.30 and has now been resolved.
Triple DES has been retired as an encryption scheme mode. It continues to be provided for us-1139
backwards compatibility. No action is required for upgrading customers who have this
encryption method configured in existing encryption schemes.
When deleting a user role in Security - User Roles, inactive user accounts are no longer bg-660
counted in the message which confirms how many user accounts are assigned to this role.
An improvement has been made to how usernames are edited in user tree-view in Security - bg-587
Users. Previously, deleting characters from the username when making an edit resulted in the
user account losing focus.

Previous Releases
Login Agent


behavior.
Object - MS Excel
A solution has been provided which prevents processes from hanging indefinitely when Actions bg-723
are being utilized and Excel has become unresponsive. If an Action cannot be completed, the
VBO will now timeout. A list of Actions with the new timeout functionality is detailed below:
• Attach
• Attach to workbook
• Open Instance
• Close Instance
• Open Workbook
• Save Workbook
• Save Current Workbook
• Save Workbook As
• Save Current Workbook As
• Close Workbook
• Close Current Workbook
An issue has been addressed whereby the Attach, Attach to Workbook and Open Instance bg-822
Actions would not function correctly when used with a specified workbook name.

Previous Releases
Utility JSON
The JSON VBO now uses an updated Newtonsoft.JSON.dll. If this version of the VBO is used, us-1184
the following points need to be considered when using the latest copy of the VBO with existing
processes.
• When binary data is used in the Collection to JSON Action, the data is now converted to
"Binary":"MTAxMDA=". When this data is used in the JSON to Collection Action an
output of the type 'text' will be created, containing the value MTAxMDA=.
• Time and DateTime data are now returned from the JSON to Collection Action using the
following formats "Time":"2017-09-26T00:00:16Z" and "DateTime":"2017-09-
22T10:32:17Z".

Blue Prism Release Notes 6.5.1 - 4.Pd

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Blue Prism Release Notes 6.5.1 - 4.Pd

Caricato da

Copyright:

Formati disponibili

6.5.

Document Revision: 1.1

Trademarks and copyrights

Commercial in Confidence Page 2 of 82

Commercial in Confidence Page 3 of 82

Version 6.0: September 2017 75

Commercial in Confidence Page 4 of 82

Introduction - Blue Prism version 6

Commercial in Confidence Page 5 of 82

Upgrading Blue Prism

Review upgrade notices

Commercial in Confidence Page 6 of 82

Commercial in Confidence Page 7 of 82

Upgrading to version 6 - Selecting a server communication method

Commercial in Confidence Page 8 of 82

Commercial in Confidence Page 9 of 82

Directly executed SQL Script (advanced)

Commercial in Confidence Page 10 of 82

Static Code Analysis VL5. Veracode Score: 100/100. Further information

Commercial in Confidence Page 11 of 82

Fixes and minor improvements

Description of change Reference

Commercial in Confidence Page 12 of 82

Visual Business Object Updates

Commercial in Confidence Page 13 of 82

Upgrading from versions prior to 3.5.25

The Blue Prism Server service must be manually deleted

Upgrading from versions prior to 4.2.16

Upgrading from versions prior to 4.2.35

Commercial in Confidence Page 14 of 82

Upgrading from versions prior to 5.0.5

Dashboards require users to have increased SQL permissions

Previous License keys will not work

Requires .NET Framework 4

Commercial in Confidence Page 15 of 82

Upgrading from versions prior to 5.0.23

Upgrading from versions prior to 5.0.24

Upgrading from versions prior to 5.0.29

Upgrading from versions prior to 6.0

Introduces WCF (Windows Communication Foundation)

Dates are now processed using different logic

Commercial in Confidence Page 16 of 82

Pending or Running sessions should be completed or cancelled prior to upgrade

A new installer has been introduced

Upgrading from versions prior to 6.3

New Default groups for Objects and Processes

New permission required to call Objects or Processes exposed as Web Services

Some programmatic options will no longer work by default

Commercial in Confidence Page 17 of 82

New mechanism for securing access to Runtime Resources

Upgrading from versions prior to 6.4.2

Snapshot isolation must by manually applied if using a script to create or upgrade a

Commercial in Confidence Page 18 of 82

Upgrading from versions prior to 6.5

Session logs are not migrated by default

Tesseract language packs must be updated

Commercial in Confidence Page 19 of 82

Invalid upgrade paths

Commercial in Confidence Page 20 of 82

Commercial in Confidence Page 21 of 82

Description of change Reference

Commercial in Confidence Page 22 of 82

Description of change Reference