|
Name
|
Unique name of the unattended robot.
|
|
Robot Type
|
Type of the robot.**Unattended**: Robot for an unattended automation.
|
|
Machine Name
|
Computer name of the physical or virtual machine on which the Unattended Robot application is installed.This field appears only when **Unattended** is selected from the **Robot Type** field.
The machine name is a string-type field that you use when you don't want to enable the **sn\_rpa\_fdn.enable\_unattended\_robot\_machine\_name\_lookup** system property.
If you enable the **sn\_rpa\_fdn.enable\_unattended\_robot\_machine\_name\_lookup** system property, this string type field changes to a reference type field on the robot form.
The machine name fetches the unique value references from the Configuration Item \(CI\) tables that are defined in the **sn\_rpa\_fdn.machine\_name\_reference\_fields** system property.
The bot process table \(cmdb\_ci\_rpa\_process\) and robot table \(cmdb\_ci\_rpa\_robot\) are excluded from the search results when you provide the names of the CI tables to reference the unattended robot's machine name in the **sn\_rpa\_fdn.machine\_name\_reference\_fields** system property.
The **Machine Lookup value change** scheduled job validates the values in the **Machine Name Lookup** field and **Machine Name** field.
For more information, see the Scheduled jobs installed section in [Components installed with RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/installed-with-rpa-hub.md) and [Configure RPA Hub properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/rpahub-sys-properties.md).
|
|
High density robot
|
Option to create multiple robots with the same machine name.The machine must support multiple user sessions at the same time so that you can run multiple automations simultaneously.
This field appears only when **Unattended** is selected from the **Robot Type** field.
|
|
Screen resolution
|
Screen resolution used by a high density robot while establishing the RDP connection before executing the automation.High density robots can operate with different screen resolutions for each robot on the same machine without any issues if they are running different bot processes. However, if all high density robots on the same machine are executing the same process and utilizing Computer Vision actions, they must maintain the same resolution. Otherwise, the automation may fail.
This field appears only when the robot is marked as high density robot.
**Note:** You can change the default value of the screen resolution using the **sn\_rpa\_fdn.robot\_screen\_resolution** RPA Hub system property.
|
|
User
|
Authorized user who can access this robot.If you're upgrading to Xanadu, the **User** field is automatically mapped with the user name \(the user\) who has recently created the process job for the selected unattended robots. If no process jobs are found for a selected robot, the robot is moved to the In Maintenance status. An RPA release manager must manually map the appropriate users to the robots.
**Note:** This field appears when the **sn\_rpa\_fdn.enable\_unattended\_robot\_user\_mapping** system property is enabled.
|
|
Department
|
Associated department of the robot. This field is automatically filled in with the information that is based on the department in the associated Attended Robot User's record.
The value in this field corresponds to the value at the time that the Robot record is created and isn’t based on real-time data.
|
|
Description
|
Brief description of the robot.
|