The license that was chosen dictates a Robot's capabilities, as follows:
- Attended - operates on the same workstation as a human, to help the user accomplish daily tasks. It is usually triggered by user events. You cannot start a process from Orchestrator on this type of Robots, and they cannot run under a locked screen. They can be started only from the Robot tray or from the Command Prompt. Attended Robots should only run under human supervision.
- Unattended - run unattended in virtual environments and can automate any number of processes. On top of the Attended Robot capabilities, this Robot is responsible for remote execution, monitoring, scheduling and providing support for work queues. When using Unattended Robots to run Parallel Processes, each Running Process consumes a separate license.
- NonProduction - retains all the features of the Unattended Robot and can only run Processes types.
- Studio - has the features of an Unattended Robot, but it should be used only to connect your Studio to Orchestrator, for development purposes.
- StudioX - has the features of an Unattended Robot, but it should be used only to connect your StudioX to Orchestrator, for development purposes.
- StudioPro - has the features of an Attended Robot and connects your StudioPro to Orchestrator for development purposes.
- Testing - has the features of an Unattended Robot and can only run Testing types.
You are able to run debugging in Studio with all types of Robots.
For more information on licensing, please see the About Licensing.
Connecting a Robot to Orchestrator offers the following benefits:
- a centralized location from which to deploy automation projects to Robots
- an easier and centralized point for the management and monitoring of multiple Robots
- the scheduled execution of automation processes on Robots
- the management of queues and transactions
- centralized Robot logging to SQL and/or ElasticSearch
If a RDP connection is started on the robot machine and this machine loses internet connection, even for few seconds, the Robot throws a “Desktop has been disconnected…” exception.
Updated 2 months ago