Blue Prism 7.2.1: August 2023

An issue has been fixed where, if a business object attempted to attach to a browser and another instance of the browser was open with a different business object already attached, there was a delay of 60 seconds before the new object was attached. The delay in attaching the second object no longer occurs.

In Process and Object Studio, when a data item is set to use an environment variable (by selecting Environment in the Exposure drop-down list in the Data Properties dialog), the list of environment variables in the Name drop-down list is now sorted correctly in alphabetical order.

Previously, an error was displayed when trying to set or check the value of a startup parameter for a specific instance of a process scheduled to run as part of a scheduled task. This error no longer displays.

If using WCF for the Application Server Controlled Resources (ASCR) callback method and the port namespace is not reserved, Blue Prism is not able to complete the login process. Previously in these circumstances, Blue Prism would become unresponsive. Now an error message is displayed informing the user of the issue and the corrective action required.

Previously, if a user selected a language other than English before logging into Blue Prism, and then logged in and tried to add or edit an Action stage in Studio that referenced an internal business object action, the selected action could not be found and a validation error message displayed. Such users can now successfully edit any processes and objects that require changes to Action stages referencing internal business object actions in any language.

Previously, it was observed that the Blue Prism application did not release handle references when running processes that interacted with browser applications. This has now been fixed so when using a Wait stage to confirm that a web element exists on the application, the number of handles associated to the Blue Prism application no longer increases.

An issue has been fixed relating to Active Directory (AD) users who are assigned to a security group that is nested under more than one group in AD, and then assigned to a role in Blue Prism. Previously, when the AD user was added to Blue Prism, the user was only granted the permissions of the first parent group to be processed; all other parent groups were ignored. This issue has been fixed and all permissions from all groups are now correctly assigned.

A similar issue occurred when moving a user from a parent group to a nested group, where the nested group permissions were not correctly synchronized, leaving the previous permissions in place. This issue is also now fixed.

A change has been made to the Blue PrismEnterprise login functionality for Active Directory (AD) users. The Sign in using Active Directory button now displays for users that are members of an AD domain even if the machines that they are using are not joined to an AD domain. Also, the button will continue to display if a domain is not detected correctly. This ensures that AD users can now log in using single sign-on even if the machine they are using is not directly connected to the AD domain.

With the 64-bit version of Blue Prism on Windows Server OS, applications that are launched using the Start Process action from the Utility - Environment VBO now launch as expected when running a process in debug mode in Studio and in Control Room.