- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot admin guide
Robot components
A UiPath Robot is built on three fundamental components:
-
UiPath Robot Service—This service is vital for maintaining the connection between the Robot and the Orchestrator, as it sends heartbeat signals at regular intervals to inform the Orchestrator of the Robot status. This communication helps monitor robot performance and manage orchestration.
-
The Executor—This is the workforce of a Robot. It performs activities within a workflow, such as clicking buttons, typing in fields, or extracting data – essentially replicating the actions a human takes on a computer.
-
The Command Line Interface—The UiPath Robot Command Line Interface (CLI) allows you to control and manage the execution of automation workflows directly from the command line, providing another method of interaction besides Assistant.
