2023.10.4

Release date: April 3, 2024

Bug fixes

Erratum - added July 3, 2024: When configuring the email settings, you were unable to save any custom configurations due to an issue with form validation. The Save button incorrectly appeared grayed out, despite having filled in all the required fields correctly. Now, you are able to successfully submit the form once all required fields are accurately filled in.
The performance of fetching items from folders with large numbers of assets has been improved.
The Path column in the UiPath.dbo.OrganizationUnits database table is updated based on the Code column. If the Code column contained incorrect or stale values for deleted child folders, the installer updated them as NULL, which violated the validation requirement at upgrade time. This mainly occurred when child folders were deleted, and their parent folders were subsequently moved. This was solved by updating the Path column based on the Key column in these scenarios, such that NULL is no longer returned.
For versions 2023.4 and up, identity/.well-known/openid-configuration is unable to load due to <add name="X-Content-Type-Options" value="nosniff" />. Therefore, you must remove it from the Identity appsettings.Production.json file.
This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).
The elevate permission check no longer includes permissions coming from disabled services. Thus, the following error no longer occurs when you attempt to assign permissions to other users: "Action forbidden: You selected at least one role that grants more than your set of permissions. Please remove the following role(s): {role_name} to continue. (#1437)".

Known issue

Added April 17, 2024

The following error can sometimes occur while trying to run the MigrateTo-ResourceCatalog.ps1 script:

This command cannot
                     be run due to the error: The system cannot find the file specified.

This only happens when the start process command tries to execute a file that cannot be located.

To overcome this issue, we recommend adding the following line to the Init-TempFolder command within the script:

$script:cliPath = Join-Path $script:cliPath "\UiPath.ResourceCatalogService.CLI.exe"$script:cliPath = Join-Path $script:cliPath "\UiPath.ResourceCatalogService.CLI.exe"