UiPath Release Notes

UiPath Release Notes

Release date: 2nd July 2019

What's New

Localization

We want to reach out to the entire world and make automation a language everyone can speak. So, starting with this release, the entire platform is available in Chinese.

Bug Fixes

  • The License Status is now properly displayed for NonProduction and Unattended machines, in the Unattended or NonProduction licensing pages.
  • Changes made to the input and output parameters of a process did not propagate to the existing associated schedules. Additionally, on the Edit Schedule window, parameters inherited from the process had their actual values displayed instead of the appropriate label.
  • We identified and fixed an issue that caused the heartbeat to malfunction if the connection to Redis was lost. Now, the heartbeat is being sent regardless of the Redis-Orchestrator connection status.
  • Processes could not be executed on Robots which were installed in user-mode if they were defined in Orchestrator only using the username. This issue did not occur if you defined your Robot using the machine\username format.
  • During a clean install, the logging configuration of the web.config file would produce the Elasticsearch index logflow-yyyy.MM where previously it was default-yyyy.MM. This had an impact on any existing dashboards and visualizations based on that index.
  • The Migrate_Deployment_Settings query used incorrect column names, resulting in potential failure of the migration.
  • Occasional deadlocks in the Orchestrator database would occur when: removing multiple packages in parallel, detecting unresponsive robots, simultaneously updating machines and deleting robots, or connecting multiple robots, with different users, on the same machine.
  • The UiPathPlatformInstaller.exe installer would incorrectly identify the localized RemoteRuntime version, and thus could not uninstall it, forcing the user to uninstall RemoteRuntime manually via ARP.

Updated about a month ago


2019.4.4


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.