Floating robots enable multiple users to use UiPath Robot on multiple workstations, as the robot is not tied to a specific machine. One user can use UiPath Robot on one machine at a time.
A user changing the workstation requires them to log out of the 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. Obviously, I cannot use UiPath Robot on multiple machines simultaneously. If I want to use a different laptop, I am required to log out of the initial session.
In classic folders, only attended robots can be of type floating.
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. Recommended 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.
Click here for more sample scenarios and the recommended Orchestrator setup in classic folders.
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. See here details about robot statuses.
In classic folders, you can use any type of standard robot (in conjunction with standard machines) and attended floating robots (in conjunction with machine templates).
Click here for license types per robot.
Click here for details on the licensing concepts.
If you have multiple Robots on the same machine, it is recommended that you group them in the same environment and Orchestrator tenant. Otherwise, some errors might occur when deploying different versions of the same process.
For more information about environments, click here.
Updated about a month ago
|Connecting Robots to Orchestrator|
|How the Connection Between the Robot and Orchestrator Works|
|Storing Robot Credentials in CyberArk|
|Fields Descriptions for the Robots Page|