- 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
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
Hardware and Software Requirements
|
Minimum |
Recommended | |
|---|---|---|
|
CPU Cores (*) |
2 x 1.8 GHz 32-bit (x86) |
4 x 2.4 GHz 64-bit (x64) |
|
RAM |
8 GB of available system memory |
12 GB |
|
Disk Space |
3.5 GB for new installations, 5 GB for upgrades (including temporary files required during installation) |
N/A |
(*) UiPath does not support the ARM architecture on Windows.
|
Supported Versions |
Particularities | |
|---|---|---|
|
Operating System |
Windows 8.1 Windows 8.1 N |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022:
|
|
Windows 10 Windows 10 N |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022:
| |
|
Windows 11 |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) | |
| Microsoft Azure Windows 10 Enterprise Multi-Session | Works in conjunction with Azure Virtual Desktop
(AVD) as well.1Supports Windows 365 machines. | |
|
Windows Server 2012 R2 |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version
(required for GIT source control)
2 | |
|
Windows Server 2016 |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version
(required for GIT source control)
2 | |
|
Windows Server 2019 |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version
(required for GIT source control)
2 | |
|
XenApp v6.5 or greater | ||
|
XenDesktop v7.0 or greater | ||
|
.NET Framework |
Version 4.6.1 or greater |
.NET Framework is required for running Windows - Legacy projects and must be installed on machines. .NET (formerly .NET Core) is a newer framework required for running Windows and cross-platform projects. The appropriate .NET version is automatically added in the installation folder when installing or upgrading Studio. If your machine runs Windows OS in a language other than English, install the corresponding language pack for the .Net framework version you are using. This is required for running Studio in any of the available languages. The .Net framework and related language pack version must correspond, and any conflicting .Net framework versions installed on the machine should be removed. |
|
Web Browsers (for browser automation) |
Internet Explorer v8.0 or greater | |
|
Google Chrome version 64 or greater |
Automated with the extension for Chrome or the Webdriver protocol. | |
|
Mozilla Firefox version 52.0 or greater |
Automated with the extension for Firefox or the Webdriver protocol. | |
|
Microsoft Edge on Windows 10 version 1803 or greater |
Automated with the or the Webdriver protocol. | |
| Microsoft Edge in IE mode (Internet Explorer v8.0 or greater) on Windows 10 version 1803 or greater | Automated with the . | |
|
Microsoft Office (for projects created in the StudioX profile) |
Office: 2013 | |
|
Office: 2016 | ||
|
Office: 2019 | ||
|
Office 365 | ||
| File System | NTFS | |
| IP | IPv4, IPv6 | Studio can be installed on IPv6-compatible operating systems. |
1 - When using
unattended robots on Virtual Machines, do not leave the Azure Virtual Desktop
sessions in disconnected state (user is connected to a host
pool in an AVD environment, but they are still connected to the session
hosts). The robot is not able to use the disconnected session as it was
created via AVD and does not have access to it. Because of this, it attempts to
create a new session to run the unattended job, but fails because the AVD
session is already created and in disconnected state. When this
scenario happens, the job eventually fails due to a time
out.
2 - This component is installed by default with the
operating system and should be reinstalled if removed.
