Edit an unattended robot in RPA Hub
Edit an existing unattended robot in RPA Hub to modify a few details of the robot, convert the robot to a high density robot, and view the robot state.
Before you begin
Create an unattended robot. Ensure to select the Robot Type field as Unattended. For more information, see Create an unattended robot in RPA Hub.
You cannot edit an attended robot.
Verify that the life-cycle stage of the robot is In Maintenance on the robot form.
When changing the robot type from high density robot to standard or vice-versa, you must reconnect the unattended robot to ensure seamless execution of automations.
Role required: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin
Procedure
- Navigate to All > Robotic Process Automation > RPA Hub Workspace.
-
Select the list icon (
).
- On the Lists tab, under Administration, select Robots.
- Select the unattended robot that you want to modify.
-
On the Details tab, update the following fields as
appropriate.
Table 1. Robot form Field Description Name Name of the robot. Department Associated department of the robot. This field is auto-populated based on the department information in the associated Attended Robot User's record.
The value in this field corresponds to the value at the time the Robot record is created and not on real-time data.
Description Brief description of the robot. 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.
Note:If you change the robot type from high density robot to standard or vice-versa, you must reconnect the unattended robot to ensure seamless execution of automations.Screen resolution Screen resolution used by a high density robot while establishing the RDP connection before executing the automation. You can have different screen resolutions for different high density robots that use the same machine name. But, it is ideal for all high density robots associated to the same bot process to have same screen resolution value.
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. -
On the form, view the states of the unattended and attended robots.
Table 2. Robot states form State Description for Unattended Robot Description for Attended Robot New Default value when a new robot is created or saved. Default value when a new robot is created or saved. Available Robot is connected to the Unattended Robot application. Attended user is connected to the Attended Robot application. Busy Robot has executed executing the automation. Attended user started the automation by selecting the run icon ( ) or desktop in desktop icon (
).
Disconnected Robot is disconnected from the Unattended Robot application. Either the attended user closed or logged out from the Attended Robot application. Unresponsive Robot runtime isn’t responding. This state occurs when the difference between current time and last heart beat time equals or greater than the value specified in the sn_rpa_fdn.robot.unresponsive property.
- Select Save.
- Optional: In the Activity and Compose fields, view the activity of the form, work notes, and additional comments.