- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
Robots
Floating robots are robots that enable multiple users to use UiPath Robot on multiple workstations, as the robot is not tied to a specific machine. With one Named User license, one user can use UiPath Robot on a maximum of three machines at a time.
A user that wants to change one of the three workstations they're working on requires them to log out of a previously used machine and log into the new one.
My name is John Smith, I am a call center operator in a team of 20 working on whatever laptop I find available when I get to work. In Orchestrator, my system administrator needs to define one machine template for the 20 laptops we have, and a floating robot using my username. This enables me to use each of the 20 laptops using my username and the key generated by the machine template.
Standard robots are the predecessors of floating robots, and you can only find them when working with classic folders. A standard robot restricts the user to use UiPath Robot on a single workstation, as the robot is tied to a specific machine, namely the one set when creating the standard robot in Orchestrator. Standard robots work only for users who always work on the same machine or whose name stays the same each time the user connects to it.
Changing the workstation requires deleting the initial standard robot and recreating it using the name of the new standard machine.
My name is John Smith, I am a call center operator working daily on the same laptop whose name is LA4324. In Orchestrator, my system administrator needs to define for me a standard machine with the same exact name as my laptop, and a standard robot using my username, robot configured to connect to the standard machine named LA4324. If I ever change my laptop, the system administrator needs to delete this robot, and create a new one, for the new machine.
Robots can automatically download processes, and execute them under custom settings. You can configure automatic process downloading, logging level, font smoothing, and resolution when configuring robot settings.
In Orchestrator there are two directions in terms of robot management, corresponding to the type of folder they operate in:
Before proceeding to robot behavior in classic folders, it is recommended that you get familiar to some basic notions first. Take a look at the following list of resources:
- The ABC of robots in Orchestrator.
- Mapping between real-life scenarios and the corresponding Orchestrator setups.
- Info about machines, what they do, their types and how to use them in relation to robots.
Robot management is done manually (Folder context > Robots), meaning you have to configure the robot and machine entities by hand. This includes:
- robot creation (includes configuration of its execution settings, licensing and authentication options)
- robot deletion
- adding a Robot to an environment such that it's able to execute processes from that environment
- removing a Robot from the environment to restrict it from executing the processes.
Unattended robots must be created manually, one for each machine/user combination in your environment.
UiPath Robot can only have access to processes found in one folder at a time. If you want it to have access to processes found in a different classic folder, you are required to delete the corresponding robot entity from the first folder, and provision it in the new one.
In classic folders, you can use any type of standard robot (in conjunction with standard machines) and attended-only floating robots (in conjunction with machine templates).
Robots can automatically download processes, and execute them under custom settings. You can configure automatic process downloading, logging level, font smoothing, and resolution in the Settings tab while creating or editing a robot.
After being created, robots can be monitored on a per-folder basis the Monitoring Robots page (Monitoring > Robots)
In classic folders, the license type of the robot is configured when creating or editing the robot entity in Orchestrator. Depending on the robot connection status, some restrictions might apply to editing.
A grouping of robots in a classic folder is called an environment and it enables you to execute the same package on multiple Robots simultaneously.
