- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Extensions
- Troubleshooting
Studio User Guide
Update Studio
The process of updating an older Studio release to this release differs depending on the Studio edition currently installed on your machine - Enterprise or Community.
The installation artifacts can be downloaded from the Resource Center in UiPath Automation Cloud, provided to you when you purchase Studio, or provided by your customer success manager or the support team.
major.minor.patch structure, which works as follows:
- The
majornumber represents the year the release is delivered in and changes with a major update. - The
minornumber is incremented each time a functionality is added, under the form of a minor update. -
The
patchnumber is incremented every time a patch containing bug fixes is released.Note: If the entire UiPath suite is installed on a single machine, and you want to update from v2018.2 or older versions, you are required to first do so on Orchestrator and then Studio and Robot. If you first update your Studio, your Orchestrator instance is removed. This is due to a change in the installers' Upgrade Code.
If you are updating from v2017.1, v2018.1, or v2018.2, note that all old local activities packages are lost. Please back up before updating.
UiPathStudio.msi installer on your machine. Your previous setup is preserved and you are not prompted to select what components to install.
None of your settings or projects are lost after doing this.
UiPathPlatformInstaller.exe to update Studio, as well as Orchestrator and Robot, on the same machine. However, please note that this installer does not
accept command line arguments.
Activity Packages
C:\Program Files (x86)\UiPath\Studio\Packages folder.
%localappdata%/UiPath/Activities folder, add the path as a feed in the Package Manager, so that the projects can reference them.
After updating from a version prior to v2018.3, Studio performs an automatic migration of dependencies when the project is opened. Read more about Dependency Migration as part of the Core Activities Split.
NuGet.config or any configuration files, and instead, UI or command-line arguments should be used. However, if manual changes were indeed
made to configuration files, it is recommended to back up these files before upgrading to a later Studio version.
%programdata%\UiPath\Activities in 2016.2 to
%localappdata%\UiPath\Activities in 2018.1 and
above.
This means that, when updating from 2016.2 to 2018.1, 2018.2, or 2018.3, the activity packs must be reinstalled to work properly. More info can be found in the Managing Activities Packages chapter.
Due to the auto-update feature of the Community Edition, any Studio activated with a Community license is automatically updated to the latest version when a new version is available on the Stable feed.
%localappdata%\UiPath installation folder is removed and the setup fails if you previously performed selections with UI Explorer in a Java application.
Please note that these issues do not occur when Studio automatically updates to the latest version.
Updating UiPath Studio is performed differently according to the type of license that is activated on your machine. There are two possible scenarios:
UiPathStudio.msi installer on your machine. Your previous setup is preserved and you are not prompted to select what components to install.
None of your settings or projects are lost after doing this.
UiPathPlatformInstaller.exe to update Studio, as well as Orchestrator and Robot, on the same machine. However, please note that this installer does not
accept command line arguments.
C:\Program Files (x86)\UiPath\Studio\Packages folder.
The Community Edition is always up to date, as it automatically updates itself as soon as a new version is available, be it Stable or Preview.
You can choose an update channel by going to Home (Studio Backstage View) > Help and selecting either Stable or Preview.
Please note that once you change your selection, you have to restart the application for the change to take effect.
%localappdata%\UiPath installation folder is removed and the setup fails if you previously performed selections with UI Explorer in a Java application.
Please note that these issues do not occur when Studio automatically updates to the latest version.
