- Introduction
- Product lifecycle
- Use of customer data in UiPath
- Use of customer data with AI Center
- Use of customer data with AI Computer Vision
- Use of customer data with Apps
- Use of customer data with Assistant
- Use of customer data with Automation Ops
- Use of customer data with Automation Hub
- Use of customer data with Autopilot for Everyone
- Use of customer data with cloud robots
- Use of customer data with Communications Mining
- Use of customer data with Data Service
- Use of customer data with Document Understanding™
- Use of customer data with Insights
- Use of customer data with Integration Service
- Use of customer data with IT Automation
- Use of customer data with Orchestrator
- Use of customer data with Process Mining
- Use of customer data with Robot
- Use of customer data with Studio and StudioX
- Use of customer data with Studio Web
- Licensing
- Commercial licensing plans
- Platform licensing
- User licensing
- Service licensing
- Licensing transition
- Delivery options
- UiPath Platform
- UiPath documentation
- Troubleshooting
Overview
Licensing transition
The names of our user licenses have changed over time. To better identify our robot licenses, check the naming progress below:
|
Year or Orchestrator version |
2018 |
2019 |
2020 |
2021.4 |
2021.10+ |
2023.10+ |
|---|---|---|---|---|---|---|
|
License |
Attended |
Attended |
Attended |
Attended |
Attended | Attended |
|
License |
Development |
Studio |
Studio |
RPA Developer |
RPA Developer | RPA Developer |
|
License |
|
added StudioX |
StudioX |
Citizen Developer |
Citizen Developer | Citizen Developer |
|
License |
|
|
added StudioPro |
RPA Developer Pro |
Automation Developer | Automation Developer |
|
License |
Unattended |
Unattended |
Unattended |
Unattended |
Unattended | Unattended |
|
License |
NonProduction |
NonProduction |
NonProduction |
NonProduction |
NonProduction | Testing |
|
License |
|
|
added Testing |
Testing |
Testing | Testing |
Testing Robots provide several advantages over NonProductions Robots, as outlined in the NonProduction and Testing Robots compared table. This section walks you through the process of moving from NonProduction to Testing, so that you can fully benefit from these advantages.
This only applies to standalone Orchestrator.
If you use the Test Automation module in an Orchestrator instance installed as an Azure App Service, read through the following information:
-
The Azure App Service installation page for general information
-
The
-testAutomationFeatureEnabledparameter description on the Publish to Orchestrator script page for details on enabling the Test Automation module
- Run the Orchestrator installer and click Change.
- Click Test Automation, and select Will be installed on local hard drive.
- Fill in the SQL server authentication information:
- the SQL server host
- the database name
- the authentication mode
- the username and password
- In Orchestrator, make the switch between NonProduction and Testing in all relevant places:
- Tenant > Machines > Edit Machine - deallocate all NonProduction runtimes from existing machines, and allocate Testing runtimes instead.
- Folder > Automations > Triggers - edit existing triggers to change all NonProduction runtime types to Testing.
- Folder > Automations > Jobs - edit existing jobs to change all NonProduction runtime types to Testing.
This is what you can expect the runtimes section of the machine page to look like after following the previous steps:
Install Test Manager.
|
NonProduction Robots |
Testing Robots |
|---|---|
|
Used for running unattended automations for development purposes only. |
Used for running unattended automations for development and testing purposes, which include workflows, activities, and applications. |
|
Run the same automations as a Production Robot, including test cases. |
Run test cases with robust verification and testing options, which can be reused across projects. |
|
Reporting must be manually configured. |
Allow for granular reporting of test case results to third party tools. |
|
Allow full workflow testing only (black box). |
Allow activity-level unit testing (white box). |
|
Allow for single points of verification. | Allow for multiple points of verification. |
| Opening Studio with
Unattended Robot or NonProduction Robot license is primarily used for
troubleshooting, with editing allowed.
You can also use it to debug projects from the development machine, with Remote debugging. | Opening Studio with Attended Robot or Testing Robot license is permitted for debugging without any editing capabilities. |
The functionality of Testing Robots is largely dependent on the standalone Orchestrator version, as outlined in this table.
|
Testing Robot/Orchestrator version compatibility |
Orchestrator 2019.10.x | Orchestrator 2020.4.x and 2021.4.x |
Orchestrator 2021.10.x | Orchestrator 2022.4.x and newer |
|
Testing Robots can execute processes. | No | No |
Yes |
Yes |
| Testing Robots can
perform white box and black box testing. |
No |
Yes |
Yes |
Yes |
|
Testing Robots can execute test automations. |
No | Yes | Yes | Yes |
|
Testing Robots support Orchestrator queue triggers. |
No |
No |
Yes |
Yes |
|
Testing Robots can execute process automations from UiPath® Apps. |
No |
No |
No |
Yes |
