Configure RPA Hub properties

Select an authentication type:- mTLS: Mutual Transport Layer Security. As a prerequisite, install the user certificate.

For more information about installing a user certificate, if you have the admin role, see Install the user-generated certificates.

• Basic: Authentication happens based on user name and password.

Restores auto session.- Type: Yes \| No - Default value: No

If it is set to Yes, then the Auto Session Restore check box on a new bot process form is selected by default. There is no impact to the existing bot processes, when this system property value is changed.

For more information about the bot process form, see Bot Process form in RPA Hub.

If enabled, when the unattended robots log in or unlock the machine to start the automation, then the machine session is restored to the original state (log off or locked) after the automation is completed.

Enables the code quality check at the instance level.- Type: Yes \| No - Default value: Yes

If it is set to Yes, then the configure the sn_rpa_fdn.restrict_package_by_severity and sn_rpa_fdn.code_quality_check_timeout system properties appropriately.

Sets a restriction on publishing package from RPA Desktop Design Studio and publishing bot process in RPA Hub. This property is effective only when code quality check feature is enabled.Select a restriction type:

• No restriction - Enables packages to publish from RPA Desktop Design Studio regardless of the code quality result. The packages with error or warning can also be published from the RPA Desktop Design Studio. Enables the publishing of bot processes regardless of the code quality result of the associated package version.
• Error - Restricts packages with Code Quality Result as 'Error' to publish from RPA Desktop Design Studio. Restricts publishing of bot process if it is using the package versions whose code quality check is marked as error.
• Error or Warning - Restricts packages with Code Quality Result as 'Error' or 'Warning' to publish from RPA Desktop Design Studio. Restricts publishing of bot process if it is using the package versions whose code quality check is marked as 'Error' or 'Warning'.

Default value: No restriction

Enables you to select one of the available machines in the CMDB table.- Type: Yes \| No - Default value: No

If you enable this property as Yes, then configure the sn_rpa_fdn.machine_name_reference_fields system property appropriately.

Note: If you enable this system property and if there are any existing robot records, to use them, retire the robot and create a new record.

Defines the frequency, in seconds, for execution logs to synchronize.- Type: integer - Default value: 60

When a new bot process is created, the default value you define in this system property appears in the Synchronize Execution Logs (seconds) field. There is no impact to the existing bot processes, when this system property value is changed.

This system property is only applicable only for those bot processes where the Track Execution Logs check box is enabled. The logs are saved locally and are synced based on the interval set in this property.

For more information about the bot process form, see Bot Process form in RPA Hub.

Defines the maximum limit for frequency, in seconds, for execution logs to synchronize.

• Type: integer
• Default value: 300

This system property is only applicable only for those bot processes where the Track Execution Logs check box is enabled and the value for the Storage field is Instance.

For more information about the bot process form, see Bot Process form in RPA Hub.

Tracks the execution logs.- Type: Yes \| No - Default value: No

If it is set to Yes, then the Track Execution Logs check box on a new bot process form is selected by default. There is no impact to the existing bot processes, when this system property value is changed.

After you enable the Track Execution Logs check box on a bot process form, the logs are captured when an automation is executed by either an attended or an unattended robot. These logs help in understanding the errors and the end-to-end logging of automation execution.

For more information about execution logs, see Bot Process form in RPA Hub.

Defines the maximum days to retain a process job.- Type: integer - Default value: 90

In a bot process record, process jobs are purged based on this system property.

Based on this system property, the maximum value for the Job Purging (days) field in a bot process is defined.

For more information about the bot process form, see Bot Process form in RPA Hub.

Defines the number of days to retain job logs.- Type: integer - Default value: 30

In a bot process record, process jobs are purged based on this system property.

When a new bot process is created, the default value you define in this system property appears in the Job Purging (days) field.

For more information about the bot process form, see Bot Process form in RPA Hub.

Ensures the attended automations to run in a Desktop In Desktop window.- Type: Yes \| No - Default value: No

If it is set to Yes, then the Enable Desktop In Desktop check box on a new bot process form is selected by default.

If it is set to No, then the Enable Desktop In Desktop check box on a new bot process form is not selected by default.

For more information about the bot process form, see Bot Process form in RPA Hub.

Forces the robot to start. - Type: Yes \| No - Default value: No

If it is set to Yes, then the Force Start check box on a new bot process form is selected by default.

For more information about the bot process form, see Bot Process form in RPA Hub.

For example, a robot R1 is assigned to multiple bot processes BP1 and BP2, and R1 is currently executing BP1. Then, if BP2, whose sn_rpa_fdn.process.force_start system property is set to Yes, is triggered forcefully and BP1 is terminated.

Ensures that the bot monitor is active. - Type: Yes \| No - Default value: Yes

This system property is set at the instance level. This property is not set at the automation level.

If it is set to Yes, then the Keep Monitor Active check box on a new bot process form is selected by default. Also the system is unlocked even after locking it.

If it is set to No, then the robot machine is locked (based on idle time settings as per the organization), when the automation doesn't have any foreground actions such as SendKeys or Mouse click.

For more information about the bot process form, see Bot Process form in RPA Hub.

Defines the expected duration for the bot process to run.- Type: integer - Default value: 60

If a value is defined here, then the same value appears in the Run Time Threshold (mins) field on a new bot process form.

For more information about the bot process form, see Bot Process form in RPA Hub.

The value in the Runtime Threshold (Mins) field on the bot process form and the configuration in this system property are used for plotting the event duration in the robot calendar.

For more information about the robot calendar, see Using the robot calendar for RPA Hub.

Ensures that the work item name is unique.- Type: Yes \| No - Default value: Yes

If it is set to Yes, then the Is Work Item Name Unique check box on a new queue form is selected by default. There is no impact to the existing queue records.

For more information about the queue form, see Queue form in RPA Hub.

Defines the default value of the Order field in the bot process.1 is the highest and 999999 is the lowest default value.

• Type: integer
• Default value: 1

Restrict robots in Assign bot process section by machine name.- Type: Yes \| No - Default value: No

If this value is set to Yes, then you can impersonate as robot from the RPA Desktop Design Studio on that specific robot machine, along with the users added in the Assigned Studio Users tab in the Robot form, if any.

If this value is set to No, then the users added in the Assigned Studio Users tab in the Robot form can impersonate as robot from the RPA Desktop Design Studio. For more information about adding the assigned studio users, see Add assigned studio users to an unattended robot.

For more information about assign bot process to an automation project, see Assign bot process to an automation project.