UiPath Release Notes

UiPath Release Notes

Release date: 28th February 2019


For those that work offline, we have some good news: you can disable the default online feeds for Robot during the deployment process. This facilitates a seamless installation process even in restrictive environments without Internet access, from the command line. For more information, access this page.

Moreover, you can now configure the location of your automation processes, for Studio and Robot, through the command line of the UiPathStudio.msi installer. This feature provides a customizable architecture to suit both strict deployments and hotseat scenarios. To read more about the newly added PACKAGES_FOLDER parameter and how to use it in your mass-deployment of Robots, see this page.

In addition to that, the UiPathStudio.msi installer enables you to easily set up your Citrix client extension with just a few clicks, as described here. If the command line is more of your thing, that's also now possible, as explained here.

Last but not least, you can now add your own activity feeds at install-time by using UiPathStudio.msi's command line. More information about the CUSTOM_NUGET_FEEDS argument and how to use it to set up your environment can be found here.

Known Issues

  • A Robot installed as a Windows Service is unable to install packages if the corresponding Packages folder is shared and on a different machine. The Robot needs to be installed in user mode, and you can find out more on this page.

Bug Fixes

  • Using the -f command to execute a process would ignore the Orchestrator activity feed.
  • The Pack command would return an error if the required dependencies were not available locally or in the NuGet download folder.
  • To ensure a smooth experience in offline environments, the list of activity dependencies has been updated in all our installers. Please note that as a result, the size of the artifacts has increased.

Updated 27 days ago


Suggested Edits are limited on API Reference Pages

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