Release date: 8 July 2020

📘

Note:

v2020.4.2 contains a security fix for an issue in releases v2020.4 and v2020.4.1. If you are using, installing or planning upgrades to either of those releases, please expedite moving to 2020.4.2 instead. More details in the Bug Fixes section below.

This release marks the General Availability of the Test Suite, giving you access to creating test cases and data-driven test cases in Studio with a Studio Pro license, enhanced management, and execution features aboard Test Manager, and the highly useful capabilities inside the UiPath.MobileAutomation.Activities package.

Upcoming Requirement Changes

Beginning with v2020.10, the TargetFramework must be upgraded to .NET Standard 2.0 from the previous .NET Framework 4.7.2 to maintain Credential Store plugin and NLog extensions functionality. See here for more details.

Improvements

We now perform a couple of additional validations upon uploading test automation packages in Orchestrator. To successfully upload such a package or package version make sure the following are true:

• The package contains at least one entry point.
• The project type is the same in between unique versions of the same package.

The X-UiPath-OrganizationUnitId header is no longer mandatory when making GET requests to the /OData/TestSetExecutions endpoint. You can now retrieve all test set executions across the folders you belong to, and only specify the header to retrieve executions belonging to a specific folder.

The Alerts.Email.SendTimeoutMs parameter has been added in web.config to help you configure the timeout duration for each email alert. The default value is 5000 milliseconds. It is used for the periodic errors email alert, daily email alert, and license expiration email alerts. See here details about the Alerts section in web.config.

To improve Orchestrator response times, you can now configure a storage bucket to add large images into when parameterizing the corresponding Create Form Task activity. Make sure to correctly configure CORS/CSP settings to access storage files.

The Azure app service installation script was further optimized, some of the zip files needed for installation being grouped or renamed. Please make sure you follow the documentation for an uneventful installation process.

Breaking Changes

When performing a silent upgrade, the Identity Server PUBLIC_URL parameter is now required.

Known Issues

• Trying to connect a v2019.4.4 or older Robot to Orchestrator throws the wrong error message when the floating robot is not defined in Orchestrator. This only occurs in classic folders when using a machine template-generated key for the connection. "There are no available licenses on the server" is displayed instead of "Robot does not exist".
• Package versions that contain the + symbol are unusable in Orchestrator as they cannot be used to create processes.
• The Explore Package option within the Packages page is disabled when using the Internet Explorer browser.
• Activating your Orchestrator license online via a proxy server is not possible as you cannot connect to the Licensing Server through a proxy. Try offline activation as a workaround.
• The estimated completion and AHT of a queue cannot be calculated for unattended robots if you quit the Robot tray, and as such, the corresponding fields on the Queues Details monitoring widget (Monitoring menu > Queues) are not populated.

Bug Fixes

• A security issue in releases v2020.4 and v2020.4.1 has been fixed in this v2020.4.2 release. We recommend that customers using, installing or planning upgrades to those prior releases move to 20.4.2 to mitigate any risk. This issue was discovered as part of our secure lifecycle development process and has not been reported to us by any customer. Releases prior to v2020.4 are not affected, and a potential attacker needs to be an authenticated user on the same tenant to take advantage of the issue. If you have any additional concerns, please contact our support team.
• SMTP email alerts were not sent after upgrading Orchestrator to v2020.4. This occurred due to SSL/TLS configuration issues. Now, selecting the Enable SSL option secures the connection by requiring a TLS certificate for the SMTP domain, while clearing it leaves the connection unsecured.
• Previously, there was no backward compatibility for the classic JobsCount and Specific strategies in modern folder API jobs. As of now, there is parity between classic folders and modern folders, hence when you run a job in a modern folder you can keep the same parameters as used for classic folders. Please note that the All strategy does not apply to modern folder jobs.
• Orchestrator administrators could not access pages associated with newly added features after upgrading to a newer Orchestrator version unless they flushed Redis cache beforehand.
• Deleting a process cleared the associated data from the Jobs chart on the Dashboard.
• Orchestrator performance degraded in environments with large form layout actions causing timeouts and increases in response times when trying to create form actions. To prevent this, you can now configure a storage bucket to add large images into when parameterizing the corresponding Create Form Task activity.
• Switching from a modern to a classic folder while creating a test set generated an exception.
• You could not add new robots or start new jobs in Orchestrator in the grace period after license expiration.
• We improved the installer experience and error messages to more clearly state the corrective action needed.
• You could not use unattended robots in attended mode with NonProduction or Testing runtimes. No issues were encountered when starting a job from Orchestrator, or when using a runtime of type Unattended.