Unattended Robot#
1. Activation Procedure#
Licenses require mandatory activation through Sherpa Orchestrator.
Local activation is available by default if the Robot has its own License that has been activated locally. To select local activation, you need to go to the Robots window and click the "Create" button above the "Robots" table:
.png)
Next, fill in the fields in the "Robot" window, selecting the Unattended role.
.png)
2. Re-activation#
Re-activation occurs automatically or at the request of an administrator, without the need for user intervention.
The transfer of the Unattended robot is carried out only through Sherpa Orchestrator.
To view or edit information for a previously created License, you need to select the desired License in the Licenses window and click the .png)
(“Edit”) button next to it. After this, a form with the settings of the selected License will open, where you can make all necessary changes:
.png)
In addition to the fields filled in when creating a new License, the editing form has additional fields:
· "Record GUID" - a unique identifier assigned to the License after its creation. This field cannot be changed;
· "Expires" - the date and time of License expiration;
· "Created" - the date and time of License creation;
· "Updated" - the date and time of License update.
3. Management#
Unattended robots are robots that are launched by the Coordinator. The Coordinator launches robots if there is work for them on the "Jobs" screen. Work can be created manually, by Trigger, or via API.
On the Robots screen, click the “Create” button and fill in the required fields:
.png)
Table 1 – User Interface Elements in the Robot Window (Unattended role)
| Interface Element | Description |
| “Robot Active” Switch | The enabled switch indicates that the Robot is active on the Orchestrator side. If the switch is in the “Robot Inactive” position, a command to turn off will be sent to the Orchestrator when this Robot requests it. |
| “Name” Text Field | The name of the robot. A required field. |
| “Unattended Role” Flag | The role of the robot. |
| “Machine (IP address or domain name)” Text Field | The IP address of the terminal server or virtual machine where this robot is deployed. |
| “Domain (if any) and account login in the format domain\username” Text Field | The domain name of the terminal server or virtual machine where this robot is deployed or the account login (if necessary including the domain) under which the robot should run. |
| “Account Password” Text Field | The password for the user Account under which the robot should run. |
| “Login and Password from Resource” Text Field | Allows specifying the login and password for this robot from the selected resource. |
| “Remote Debugging” Checkbox | Indicates that the robot will run in remote debugging mode through Sherpa Designer. |
| “Designer Machine IP Address for Remote Debugging” Text Field | The IP address of the machine where Sherpa Designer is located, through which the robot will run in remote debugging mode. |
| “Remote Debugging Server” Text Field | The server where remote debugging of this robot will take place. |
| “Coordinator” Text Field | The instance of the Coordinator that will be used to launch this robot. |
| “Description” Text Field | A description of the robot. |
| “Access Folder” Text Field | Allows specifying the access folder for the created robot. |
| “License” Text Field | Allows selecting the type of License for the robot. Available options:
|
Next, you need to create a Coordinator. The Coordinator is a service used to launch Unattended robots in user accounts where automatic login to Robot accounts is required. It is installed from the corresponding Sherpa Coordinator distribution provided by the vendor and does not require a separate License. To install it, follow the link: https://docs.sherparpa.ru/sherpa-orchestrator/razvertyvanie-platformy-pod-upravleniem-orkestratora/ustanovka-sherpa-rpa-coordinator
.png)
Table 2 – User Interface Elements of Sherpa AI Server (Coordinator role)
| Interface Element | Description |
| “Robot Active” Switch | The enabled switch indicates that the Robot is active on the Orchestrator side. If the switch is in the “Robot Inactive” position, a command to turn off will be sent to the Orchestrator when this robot requests it. |
| “Name” Text Field | The name of the Coordinator. A required field. |
| “Coordinator Role” Flag | The role of the Coordinator. |
| “Description” Text Field | A description of the Coordinator. |
| “Access Folder” Text Field | Allows specifying the access folder for the created robot. |
To save the created robot, after filling out the form, you need to click the “OK” button.
3.1. Launching the Robot via Triggers
You need to go to the “Triggers” screen and configure the robot launch in the “Robots” tab:
3.2. Launching the Robot via Jobs
You need to go to the “Jobs” screen and configure the launch:
3.3. Launching the Robot via API
The robot can be launched via API by creating a job or adding a task to the queue, for which a trigger is set to launch this robot upon receiving a new task: