Blue Prism 6.7: February 2020

Users can now secure Blue Prism application server configuration files using certificate encryption:

• A new Encryption settings option has been added to the Blue Prism Server configuration dialog in BPServer.exe. Clicking Encryption settings displays a new Select Encryption Method dialog which gives users the option to apply certificate encryption to Blue Prism server configuration files. This new mechanism is recommended for deployments that need to be the most secure and it requires a locally-deployed certificate with associated private keys to be available. The existing used built-in method is still available and this option Use default Blue Prism encryption is selected by default.
• The new AutomateC command /configencrypt enables users with the Security - Manage Encryption Schemes permission to apply a different encryption method or a new certificate to the Blue Prism server configuration from the command line. The previously used method, Blue Prism’s built-in encryption, is selected by default. The /configencrypt command must be entered from the Blue Prism install location and can be used to:
  • Display the current encryption method being used for the server configuration.
  • Change the server configuration method to certificate encryption.
  • Change the server configuration method to Blue Prism’s legacy in-built encryption method.  

Further details about this functionality can be found in the product help.

The charts displayed on the Blue Prism dashboard have been made clearer, more intuitive, and interactive. Any existing charts will be automatically updated using the new chart styles when version 6.7 is installed. The new charting functionality brings the following additional benefits:

• The introduction of a new line chart type, compatible with all data types, enables users to visualize data comparisons and trends.
• Charts now include tooltips that provide detailed information on data value and source for any data point on mouseover.
• A placeholder image displays when the data required to generate a chart is unavailable. (The zoom function is unavailable in this event.)
• Column charts axis labels are now clearer.
• A new color scheme has been introduced to improve accessibility.
• If Blue Prism is running on a device in high contrast mode, the dashboard now automatically displays in high contrast mode.
• The stacked bar/column chart option is no longer available, and any existing stacked bar/column charts will be replaced with the bar/column chart type.

Changes have also been made to improve the ordering and display of dashboard tiles and chart data:

• Daily productivity tiles now display in ascending date order.
• Tiles with work queue or table names as their axis now display in alphabetical order.
• Tables with day/month names as their axis now display in day/month order.

The Switch row/column check box has been removed from the Dashboard Tile properties dialog as it is no longer relevant to current, or previous chart functionality.

The File > Import menu option has been extended to allow multiple object and process files to be imported at the same time. The following two new menu options have been added:

• File > Import > Process / Object – launches the new Import Process or Business Object wizard, which enables you to import multiple processes and objects (from the same location) at the same time.
• After the files have been imported, the new Import Report screen lists all the processes and objects that have been imported, whether the import was successful, and any issues resolved during the import. The report can be exported to a CSV file by clicking Export.
• File > Import > Release / Skill – launches the Import Release wizard. Individual release and skill files must still be imported separately.

The import wizards use existing import functionality, unless stated otherwise. The behavior of imports executed via the command line has not changed.

To make the import process quicker and easier, BPSKILL and BPRELEASE file types are now associated with the Blue Prism client. Multiple files in the same location can also be selected at the same time and will be imported consecutively. By default, if the user is not logged in to a Blue Prism client and double-clicks a file of either type, they are prompted to log in and the import process automatically starts.

If a user is logged into the Blue Prism client and double-clicks a file of either type the import process starts automatically.

The import process may not automatically start if the first instance of an interactive client opened in this session has been closed. This is because the associated import service runs on the first instance of an interactive client opened in a given session. If multiple clients have been opened in one session, but the first instance in that session has subsequently been closed, a new instance of Blue Prism starts and the user is prompted to log into import the file. As with any import, the appropriate permissions are required.

A new My Profile tab has been added to Blue Prism to enable users to manage their password or sign out of Blue Prism via the following menu options:

• Change Password launches the new Reset Password wizard, which prompts users to enter their current password, followed by their new password.
• Sign Out logs the user out of their current Blue Prism session.

The My Profile tab is not visible for users whose Blue Prism login credentials use single sign-on.

A new tab has been added to Blue Prism, which when clicked, opens the Blue Prism Digital Exchange in the user’s default browser. The Digital Exchange tab is visible by default, but can be hidden by selecting the Hide the Digital Exchange tab option in the System > System - Settings screen.

The following enhancements and fixes have been made to the Blue Prism enterprise, trial, and learning editions:

• The Blue Prism installer has been updated to improve accessibility and make the install and upgrade process easier.
• When installing for the first time, the language selected in the installer is now automatically set as the default language in the Blue Prism client. However, if Blue Prism has previously been installed, the language settings selected for the existing installation are retained.

We have made some improvements which make it easier to manage updates to Blue Prism environments. The following changes have been made as part of this enhancement:

• A new report called Environment Summary has been added to System > System – Reporting to support the improved patch functionality. For each component, the report lists the Blue Prism version, component type, when that component was first connected, and when it was last updated.
• Data for the Environment Summary report is only collated if the new Save environment data for clients, runtime resources and servers to the database option in the System > System - Settings screen is selected. This option is selected by default, and the data is recorded in a new database table, BPAEnvironment, for all interactive clients, runtime resources, and application servers on start up.
• The About option in the Help menu now also includes the full Blue Prism version number to enable users to quickly see which patch has been applied.

• Improvements have been made that may make it possible in the future to deploy certain patches to only the affected devices.

A new server-based HTML5 version of the help has been created to replace the current in-product help system. This provides users with a more contemporary, easily accessible user interface that includes enhanced features and provides a better user experience. The new help has a responsive, flexible layout that can be viewed on different types of device, such as mobile phones. As the help is now independent of Blue Prism releases, the content can be updated as and when required, ensuring the information is accurate, up-to-date, and addresses the needs of users.

The functionality of Blue Prism and content of the help system are largely unchanged – when the help is called, either from the help menu or by pressing F1, the appropriate topic of the web-based help displays. Release notes, the installation guide, and a number of other feature guides are now additionally available from the help. The content is available in Japanese, Chinese, and French, automatically reflecting the language selected in the Blue Prism user interface.

For users who do not want to access the new web-based product help online, or want to provide the help locally within their environment, the Enable Offline Help option has been added to the System > System - Settings screen. This is a system-wide setting, which applies to all Blue Prism devices connected to the environment, meaning the help must be stored in a location which is accessible to all devices.

The help files can be obtained from the Blue Prism Portal page for this release. The available offline files will be updated to include any major changes to the online version.

A number of changes have been implemented to enhance the performance of the tree control in Studio and Control Room, for example:

• Load time has been reduced when running with large numbers of objects and processes by not refreshing the entire tree when an item is selected.
• The number of instances where translations lookups occur has been optimized when interacting with the tree view. This improves responsiveness when there are a large number of nodes.
• The time taken to open, save, and close processes in Studio has been improved.

The following enhancements have been made to the Work Queues internal business object:

• A new action called Get Item By ID has been added, which retrieves items from work queues using their unique item ID. This enables a specific work queue item to be retrieved if its ID is known, without needing to loop.
• A new input called Resource Name has been added to the Get Exceptioned Items action, which can be used to filter exceptioned items by resource. If left blank, all exceptioned items for this queue are returned, as per existing functionality.

The Blue Prism interactive client user interface and product help are now available in French. When starting Blue Prism, the user interface is automatically presented 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 France and Canada are now available in calendars by selecting the required region in the System > Calendar settings.

A new field Retype the password to verify has been added to the Credential Details dialog to ensure the user has typed the password accurately when creating new credentials. This change does not impact credential creation via command line as the entered password is visible.

A new date range filter has been added to the System - Archiving screen. The filter defaults to the previous seven days, improving performance when the screen loads.

The Application Model timeout functionality for external Application Manager modes has been extended so that Wait stages now observe the configured timeouts. Read, Write, and Navigate stages continue to apply these timeouts.

Audit logs have been enhanced to include more information relating to the creation, deletion, and amendment of credentials. The credential type and password status are now included in the audit logs. Also, the comments field is no longer written to a credential deletion event, as it is not pertinent to the deletion and has already been recorded.

Additional validation has been added to the Connection Configuration screen so users are notified if insufficient information has been entered when creating and upgrading databases.

A warning message now displays if Enable Unicode support for session logs is not selected in System Settings and the user changes their Blue Prism regional locale settings to Chinese, Japanese, or French. If this option is not selected, any Kanji characters in the process logs or audit records will be incorrectly stored as question marks.

A new report called Logging has been added to System - Reporting. The report lists all processes and objects in the current environment, the number of stages in each of those items, and how many of those stages have logging set to Enabled (as a number and a percentage).

A new Port field, displaying the default port number, has been added to the Data Gateways - Settings screen to enable users to amend the SQL port used by Data Gateways without the need to use the advanced configuration functionality.

When editing a Data Gateways output that contains an HTTP endpoint type, the selected HTTP method is now retained. Previously, the HTTP endpoint reverted to the default Put HTTP method when the wizard launched.

A new Auth Type column has been added to the user list on the System > Security - Users screen. This will be populated automatically and shows whether each user account is configured for Blue Prism authentication or single sign-on.

The following issues with Firefox 68 have been resolved:

• Blue Prism is now fully compatible with Firefox 68, allowing web pages and applications running in Firefox to be automated. Firefox 68 included a change to close the first instance of Firefox immediately after launch and open a second instance. As Blue Prism attached to the first instance, this prevented it from launching and then successfully automating a process.
• The instance of Firefox that opens when installing the Blue Prism Firefox extension now automatically closes following installation.

The following updates have been made to Multi-Team Environments functionality:

• The Manage Access Rights permission is no longer required to move objects and processes between groups that share the same restricted ancestor. This corrects the logic in previous releases where the permission was required even though such moves do not affect the access rights of any object or process in these groups.
• The Edit Process Groups and Edit Object Groups permissions have been updated to allow users with these permissions to delete sub-groups in restricted groups for which they are assigned these access rights.
• In the Manage Access Rights screens, the Import Object and Import Process permissions now correctly display as uneditable and accurately reflect the setting applied by the selected user role. These are administrative permissions granted by user roles and cannot be edited at group level.

The following changes have been made to the Remove From Group option:

• When selected for an object, the item is now correctly moved to its respective default group rather than appearing to be removed from the tree entirely.
• The permissions check, performed when this option is selected in the objects tree in Studio, has also been updated to confirm that users have the required permissions on the default object group to complete the move. Previously, the permissions check for objects was incorrectly performed on the default process group.
• When selected on items that do not have default groups (users, tiles, and work queues) an error no longer occurs and the item is now correctly moved to the root of the navigation tree.

An issue where the Blue Prism server services attempted to start using the 'Default' server configuration, rather than the configuration specified in BPServer.exe, has been resolved. In this scenario, services attempted to connect to the server using the wrong connection settings, or if the ‘Default’ configuration was already in use, the service would fail. This issue applied to Blue Prism 6.6 environments where both individual or multiple services were configured.

All output types that are configured to be sent to Data Gateways are now included in the outputted data, regardless of whether the Send published dashboards to data gateways option is selected. Previously, only published dashboard data was sent to Data Gateways if this option was selected, and any other selected outputs were not included.

Processes and Objects will only be opened from the database if the latest copy is not already available in the local cache. This reduces network communication and improves the time taken to open processes and objects.

A new input parameter called Batch Size has been added to the Add To Queue action, which enables users to add multiple items from a collection to a queue in batches, rather than all items at once. A value of 0 will process all items in one batch. If a value is not specified, a default batch size of 1000 will be used.

The Add Queue Item action no longer removes leading or trailing spaces from work queue item Key values. This ensures consistency between the Get Next Item and Add Queue Item actions, preventing errors when executed in the same process as the Get Next Item action does not remove these spaces.

An issue in Object and Process Studio, where entering more than 255 characters in the Value field for a ‘Text’ input parameter in Action, Page, or Process stages incorrectly prevented the stage from being saved, has been resolved. Previously, if the Value field contained more than 255 characters, a validation message displayed, preventing the stage from being saved.

Users no longer require edit permissions to import objects and processes that overwrite items that already exist in the database. This addresses an issue which was originally fixed in 6.4 and was then incorrectly reverted in 6.6. This functionality now works as intended, edit permissions should not be required when importing objects and processes that already exist in the database.

For further details see Permissions required to overwrite objects and processes on import.

The expiry date of the user credentials now saves correctly when modified in the Credential Details dialog. Previously, when the credential was saved, the date was reset to the initial value.

Previously, when running a process with an Add Row action and opening the action stage properties, an error occurred if the collection contained a nested single row collection. This has now been addressed by adding a default row when using a single row collection.

An issue where the default resource wouldn’t connect in Control Room following consecutive logins to Blue Prism by two or more different users has now been addressed.

An issue has been addressed where passing a DateTime value into a process as a startup parameter could result in the incorrect termination of a session when attempting to log the details of the start stage to the database. This only occurred when an application server was configured to operate in a time standard other than UTC.

If a nested collection is created and then the Blue Prism regional locale setting is subsequently changed to Japanese, users can now successfully add an initial value to the existing nested collection. Previously, attempting to do this would result in an unhandled exception error, as field names could not be successfully retrieved from the existing nested collection properties.

If a user changes Blue Prism’s regional locale setting to a different language, that language is now retained on the Connection Configuration screen. This setting was previously only retained for users with elevated privileges on the local device.

An issue has been addressed where applications located in folder paths that contained Unicode characters could not be launched via the Application Modeller.

The Application Modeller now correctly displays the Attach button if the model is configured to attach to an application that is already running. Previously, the Launch button incorrectly displayed until the Application Modeller had been restarted.

An issue has been fixed where a web page launched via the Application Modeller did not display if the URL contained Japanese characters.

In Blue Prism versions 6.4.2 to 6.5, when using the Application Modeller to spy applications that contained Unicode characters, null characters were incorrectly added to some element attributes for the application. This issue was addressed in version 6.5, so that such elements were correctly spied, despite the additional null character. However, any object created prior to that fix, when used in Blue Prism 6.5 or later would cause an error when the element was highlighted in the Application Modeller. This has now been fixed and the erroneous null characters are removed from affected elements during import.

Previously, entering multiple, consecutive asterisks (*) in the Value field of an element in the Application Modeller resulted in an error when trying to highlight an element that had already been spied. To address this issue, multiple, consecutive asterisks are now treated as text, and single asterisk characters as wildcards.

In the Application Explorer tree of the Application Modeller, right-clicking an element and then selecting Insert New no longer creates a new Dynamic Data Exchange (DDE) element. A DDE element is only created once the user has selected the DDE Element option in the sub-menu.

Clicking OK in the Region Editor of the Application Modeller when a filter has been applied to the Application Explorer no longer results in an error.

The GetClipboard() function now accurately reads Unicode characters. Previously, this function replaced retrieved Unicode characters with question marks.

Objects using the Attach action now successfully attaches to windows presented in Windows Explorer that have Unicode characters in their title. This action previously failed because Unicode characters were replaced with question marks when retrieving the window’s title.

An issue where Unicode characters were being stored as question marks in archived session logs has been resolved. This issue affected Unicode characters in the result field of the BPASessionLog_Unicode database table and occurred regardless of whether the Enable Unicode support for session logs check box in System - Settings was selected.

The AutomateC.exe /resourcestatus command now runs successfully, regardless of the length of the longest resource name. Previously, the command could not be processed if the longest name of the resources being checked was fewer than seven characters.

An event log entry is no longer created when a user attempts to create a work queue with an existing name using the AutomateC.exe /createqueue command.

Users can now set a maximum recursion level in the Automate.exe configuration for elements modeled via the Active Accessibility (AA) mode. The default value is 100: <add key="AA.Mode.MaximumRecursion" value="100" />. This allows users to cater for scenarios where an object could enter an infinite loop when attempting to pass over some unsupported web elements in order to reach the element it was trying to highlight.

The permissions check, performed when the Remove From Group shortcut menu option for objects is selected in Object Studio, has been updated to confirm that the user has the required permissions on the default object group to complete the move. Previously, the permissions check for objects was incorrectly performed on the default process group.

An unnecessary check for Audit – Process Logs and Audit – Business Object Logs permissions is no longer carried out when using the GetResourceName function in a Calculation stage. Previously an unhandled error displayed if users did not have these permissions.

An audit event is no longer created when a process marks a queue item with an exception. An audit event is now only created for queue items that are manually marked with an exception.

An issue that resulted in duplicate resource entries displaying in the Credential Details screen if a resource was in multiple groups has been addressed.

An isolated case of an intermittent system null reference exception error no longer occurs when running processes in Control Room that reference VBOs.

Processes and objects in Studio are now listed in their groups in alphabetical order. Any new processes and objects will also be listed in alphabetical order, rather than the order in which they were created.

Previously, ‘No report content available’ was incorrectly displayed on the first line of all reports generated in Blue Prism. This line now only displays in reports with no content.

When importing an object, individually or as part of a release, any incoming application element groups that have the same ID as an existing group are automatically assigned a new ID. This change ensures that errors do not occur when importing application element groups with duplicate IDs – an issue that was evident when such objects, created in Blue Prism 5.x, were imported into 6.x versions.

Users can now delete text from any password field by holding down the Ctrl key and pressing the backspace key twice on the keyboard. This action previously resulted in an error.

In Object and Process Studio, using the Evaluate Expression feature within the Calculation Stage properties no longer incorrectly removes '&' characters from the results. The returned value now matches the value that would be obtained at runtime.

Previously, logging image data during surface automation resulted in intermittent errors. This issue has now been resolved.

A memory leak issue which occurred when spying an object that contained a Navigate stage configured with a Verify action and with Highlight set to True has been addressed.

When an object or process is automatically recovered and viewed in the comparison tool, the last manually saved object or process now displays in the left-hand pane and the last automatically saved item in the right pane. This adds clarity as the items display in chronological order from left to right.

The auto-save backup time has also been corrected – previously it added an hour to the actual time of the backup.

The license activation wizard is now only accessible to users that have the necessary System - License permission. If a user without this permission logs into an unlicensed Blue Prism client they are unable to access the System - License screen. Users in this scenario only have access to the Home, Digital Exchange, and My Profile tabs.

Previously on the System - Archiving screen, an error occurred when users attempted to view session logs that had been archived by another user. Users are now notified that archived session logs are no longer available for viewing.

In Object Studio, saving the output from a Read stage to a collection no longer results in a validation error. This issue only occurred if the value of a field within the collection had a data type of Flag, and in environments running Blue Prism version 6.5.0 and later.

The start and end times of archived session logs are now correct when a log is restored. Previously, the time zone offset applied to the log was not saved with the archive, which resulted in it incorrectly being reapplied when the session log was restored.

As per existing behavior, an offset of 0 UTC will be applied to imported session logs that have been exported from a previous version of Blue Prism and do not have an offset archived.

The ability to sort audit logs in ascending or descending order by clicking the column header has been restored. This functionality has been unavailable since version 6.2.0.

An audit log Tesseract engine setting changed to: [n] is no longer incorrectly created when the System - Settings screen has loaded but no changes have been made.

An audit log is now generated only when the Allow latest Runtime Resource screen capture and/or Prevent registration of new Runtime Resources settings in System - Settings are changed. Previously, if the values for these two settings had been updated, an audit log was generated every subsequent time the System - Settings screen was accessed.

In Studio, users are now prevented from creating groups named "Objects" or "Processes". Any pre-existing custom groups with these names must be renamed, otherwise the previous restriction where the groups cannot be moved within the hierarchy will apply.

In the Connection Configuration dialog, the Cancel button no longer incorrectly validates the Connection Name field.

In the Connection Configuration dialog, if users enter an invalid value in the Additional SQL Connection Parameters field, they are now prompted to enter a valid parameter or clear the field before proceeding. Previously, entering invalid parameters resulted in an error.

In Object Studio, clicking the initial action in the properties dialog for a Write stage no longer incorrectly changes the data type for that action to 'Unknown' and the correct data type now displays. This issue did not affect the functionality of the object.

Invalid Write stage expressions are now detected when using the Debug > Validation menu option in Object Studio. Previously, expressions were not validated when performing the validation via the Debug menu.

When processes or objects are running during a debug session in Studio, the Save As option is now disabled as saving the process or object with a new name caused any locks held on work queue items to be lost. Additional logic has been added to the Save option to ensure all locks on work queues are retained when modifying a process or object during a debug session.

When using a Blue Prism runtime resource to configure users or permissions within a Blue Prism deployment, using the Set Item Checked action in a Navigate stage to set the permission for a Blue Prism user role no longer results in an error when attempting to select or clear a check box that is already selected or unselected.

When generating a new report via System - Reporting, if the user chooses to overwrite an existing report, the entire report is now overridden. Previously, if the existing report had more lines than the new report, then those lines remained at the end of the new report.

When viewing the dependencies of a collection or data item stage in Process or Object Studio, stages that are created on different pages using the same stage type and name, are no longer referenced as a dependency if Hide from other pages in the process has been selected for that item.

Locked queue items are now correctly included in the pending column on Queue Volumes Now tiles. Previously, this data was not included in the BPDS_QueueVolumesNow data source.

From a sub-page in Process Studio, clicking Step Out on an End stage that has a breakpoint applied now successfully moves to the parent page. Previously, clicking Step Out incorrectly created a continuous loop of the stages on the sub-page.

When triggering objects or processes that are exposed as a web service, they will now run consecutively, rather than simultaneously, when configured with an Exclusive run mode.

The way that runtime resources handle requests to objects or processes that are exposed as web services has been updated to reduce scenarios where the runtime resources could become unresponsive. This improvement applies when using auto-initialization to consume the exposed web services.

When using the comparison tool to view different versions of objects or processes any changes to Multi Calc stages are now highlighted. Previously, amended Multi Calc stages were not highlighted.

To improve connection stability and reduce the occurrence of dropped connections, the resilience of the connections from the interactive client and the application server schedulers to the runtime resources has been enhanced. This prevents an intermittent issue where sessions that had not been successfully started were being incorrectly disconnected, leaving the session in a ‘Pending’ state by the scheduler.

Multiple parametrized query errors are no longer intermittently generated and written to event logs when a user logs out of Blue Prism. Previously, these errors occurred if a user logged out of Blue Prism whilst Control Room sessions were refreshing in the background.

Using a Calculation stage to write a value to a nested collection no longer causes a validation error.

When checking which Internet Protocol (IP) address type to use for external communications, the Blue Prism local host now correctly detects whether the network interface is configured to accept IPv6 format addresses for communications, rather than whether that format is supported. If IPv6 is not accepted then the IPv4 address type is used, this prevents an issue where Blue Prism was attempting to communicate using an incorrect IP address type.

The Edit Service, Delete Service(s), and Find References options on the System > Objects - Web API Services screen can no longer be selected if there are no services listed on the screen. This change prevents an issue where clicking these options resulted in an error if no services had been added.

The user permission Audit - View Design Controls now allows users to view, but not amend the System > Audit - Design Controls screen. Previously, this permission did not prevent users making and saving changes on the screen.

When loading recovered, auto-saved object or process files, the correct files are now successfully loaded and the auto-save functionality continues working. Previously, the last manually saved object or process files were loaded instead of the auto-saved files.

To retain existing functionality, but promote security roles as the recommended credential access method, (legacy) has been added to the Processes and Resources tab names in the Credential Details dialog’s Access Rights tab, accessed via the System > Security - Credentials screen.

The following minor improvements have also been made to the Credential Details dialog as part of this enhancement:

• The All option in the Security Roles tab has been renamed All Roles.
• A link to the product help has also been added to the descriptive text on the Access Rights tab.

An updated version of the Credential Manager data sheet has been published to reflect the latest updates, changes, and recommendations.

When saving changes made in the User Settings dialog (accessed via the System > Security - Users), users are no longer prompted to change the password if they click into the Enter a password field without entering a new value. Previously in this scenario, an erroneous message displayed and changes could not be saved without first changing the password.

The caps command, used each time a Blue Prism interactive client establishes a connection with a runtime resource and originally introduced to support interaction with binary business objects in version 3, is now disabled by default to improve performance.

Archived session logs are now clearly marked in the Schedule Log Viewer and a tool tip informs users that they must be restored prior to viewing.

The sorting by Lock Date on the Unlock Processes screen now works as expected.

Using the Compare to a process or business object in a file option in the Process/Object Comparison wizard no longer results in errors.

An issue has been addressed where an error occurred when attempting to highlight any differences in labels (e.g. for Wait stage links) when comparing two versions of a child object which referenced the application model of a parent object.

Blue Prism administrators are now prevented from deleting a user that is currently logged into either a Blue Prism interactive client or a runtime resource on the same computer.

The Stage logging drop-down list in the Action Properties dialog has been updated so when Disabled is selected, the adjacent Don't log parameters on this stage check box remains unchecked and grayed out after saving. Previously, although the check box was set to Disabled, when returning to the Action Properties dialog, it did not appear disabled and could be selected (without actually applying the setting).

When importing processes or objects, individually or as part of a release, any resolution options selected in the Resolve Import conflicts page are now retained if a user clicks the Back button and subsequently returns to that page of the import wizard.

The function that refreshes Studio to display changes made to environment variables via the System > Objects - Environment Variables screen has been rewritten to preserve information cached on process/object opening. This addresses an issue where changes made to environment variables were not being applied until the user logged out of Blue Prism.

In Blue Prism 6.6, the update frequency of the runtime resources that interact with User Interface Automation elements was changed to be reduced when not running a process. This frequency reduction was applied when the process was running rather than when it was not. This has been addressed so that the frequency update is applied to the correct state.

The Open and Close pages now publish successfully if the Publish this page as an Action option in the Page Information dialog is selected. Previously, the Open and Close pages were not published, regardless of the option being selected.