List of settings in Pega Robot Manager
-
- Last UpdatedSep 29, 2023
- 11 minute read
List of settings in Pega Robot Manager
Settings for Notifications
Thresholds
Threshold | Threshold figure (default) | Purpose |
---|---|---|
Robot automation execution is 20% longer than expected | See the relevant threshold in the Notification column. | If the system reaches a threshold, Pega Robot Manager sends an appropriate Notification to users through a web gadget or email. |
Robot queue is at 80% of capacity | ||
Robotic automation reached 80% of service-level agreement (SLA) deadline | ||
Robot automation failure count is 80% of threshold | ||
Robot consecutive automation failure count is 80% of threshold | ||
Robot reached 80% of not ready threshold |
Intervals
Interval | Interval period (default) | Purpose |
---|---|---|
Notification alert | 30 minutes | The Notification alert interval prevents the system from sending repeated Notifications of the same type and possibly for the same operator. The interval defines the period of time that must pass before the same Notification is re-sent. |
Recipients
Notification | Notification figure (default) | Purpose |
---|---|---|
Robot automation execution is 20% longer than expected | See the relevant threshold in the Notification column. |
Notification is:
|
Robot automation failure count is 80% of threshold |
Notification is:
|
|
Robot loses connectivity |
Notification is:
|
|
Robot consecutive automation failure count is 80% of threshold | Notification is: Note that the robot assignments failures count is
reset at every restart.
|
|
Robot reached 80% of not ready threshold |
Notification is:
Note that the the system resets the robot's not ready start time if a robot heartbeat message with application status set to true is received by Robot Manager. |
|
RPA Service not heartbeating |
Notification is:
|
|
Robotic assignments reach 80% of SLA deadline |
Notification is:
Click to see the % deadline. |
|
Robot automation timed out |
Notification is:
When the maximum execution time is exceeded, the Assignment is pulled from the robot and sent to the time-out work basket. Click to view Assignments in the time-out work basket. |
|
Robotic assignment past SLA deadline |
Notification is:
You can define an SLA in any one of the following ways:
|
|
Robot queue is at 80% of capacity |
Notification is:
|
|
Scheduling service is down |
Notification is:
|
Settings for Data retention
Operational Statistics
Usage interval | Enabled (default) | Purpose |
---|---|---|
Ingest hourly usage statistics | True | The system stores usage information by the hour, which allows for reporting at hourly intervals. |
Ingest daily usage statistics | True | The system stores usage information by the day, which allows for reporting at daily intervals. |
Ingest monthly usage statistics | True | The system stores usage information by the month, which allows for reporting at monthly intervals. |
Ingest yearly usage statistics | True | The system stores usage information by the year, which allows for reporting at yearly intervals. |
Data archiving settings | Interval (default) | Purpose |
---|---|---|
Health data | 7 days |
Settings define the period of time for which these statistics and operational data are saved. |
Exceptions | 45 days | |
Usage data: hourly | 48 hours | |
Usage data: daily | 30 days | |
Usage data: monthly | 24 months | |
Usage data: yearly | 4 years |
Data purging settings | Interval (default) | Purpose |
---|---|---|
Health data | 14 days |
Settings define the period of time for which these statistics and operational data are saved in the archive tables. |
Exceptions | 60 days | |
Usage data: hourly | 96 hours | |
Usage data: daily | 60 days | |
Usage data: monthly | 48 months | |
Usage data: yearly | 8 years |
Usage telemetry
The following settings are inherited by default from the built-on application:
Data purging settings | Interval (default) | Purpose |
---|---|---|
Daily robotics telemetry data retention | 1 month |
These settings define the period of time for the applicable data is saved in the Usage telemetry tables. |
Monthly robotics telemetry data retention | 2 months | |
Yearly robotics telemetry data retention | 1 year |
Unattended RPA
The settings in the following tables apply to all applications in the system:
Data archiving | Interval (default) | Purpose |
---|---|---|
Robotic work group and assignment type audit | 90 days |
Number of days to preserve audit data for work groups and assignment types before archiving. |
Robot activity and underperforming robots | 7 days |
Number of days to preserve data for robot activity and underperforming robots before archiving. |
Robot events | 100 events per robot |
Number of events per robot to preserve before archiving |
Robot automations | 10 Automations per robot |
Number of Automations per robot to preserve before archiving |
Data purging | Interval (default) | Purpose |
---|---|---|
Robotic work group and assignment type audit | 90 days |
Number of days to preserve audit data for work groups and assignment types before archiving. |
Robot activity and underperforming robots | 365 days |
Number of days to preserve data for robot activity and underperforming robots before purging. |
Robot events and automations | 90 days |
Number of days to preserve records for robot events and Automations entries before purging. |
Attended RPA
The settings in the following tables apply to all applications in the system:
Data archiving | Enabled (default) | Purpose |
---|---|---|
Attended RPA audit | 30 days |
Number of days to preserve attended Automation audit data before archiving. |
Data purging | Interval (default) | Purpose |
---|---|---|
Attended RPA audit | 90 days |
Number of days to preserve attended Automation audit data before purging. |
Settings for Attended RPA
Dashboard
Application setting | Interval (default) | Purpose |
---|---|---|
Goal for usage trend | 65 % | Defines the thresholds for settings that are displayed on the Dashboard. |
Goal percentage of users using Attended RPA | 98 % | |
Percentage for average health | 95 % | |
Percentage for good health | 75 % |
Intervals
Interval name | Interval period (default) | Purpose |
---|---|---|
Attended RPA heartbeat interval | 3600 seconds | Defines the time period between system heartbeats for attended Automations. |
Settings for Unattended RPA
Intervals and thresholds
Usage interval | Interval/threshold (default) | Purpose |
---|---|---|
RPA service heartbeat | 30 seconds | Defines the time period between system heartbeats for unattended Automations. |
Not ready threshold | 10 minutes | Defines how long a robot can spend in the APPLICATION NOT READY status before being stopped by Robot Manager. |
Allowed wait time for robot registration | 120 seconds | Defines the expected time for the RPA service to start up Runtime. |
Robot heartbeat | 30 seconds | Defines the frequency at which the robot sends the heartbeat message to the Pega server. The value is also used to deliver Stop commands, Profile commands, and to notify that there is a change in settings. |
Underperforming robot timeout | 60 minutes | If a robot is stopped by the system because the robot is underperforming, the robot cannot be restarted in the same work group until after this timeout period expires. |
Max starts issued per schedule action | 4 starts | Defines the maximum number of attempts to start a robot on the basis of a schedule. In this case, the START command can be issued either by configuring a MOVE Action or by any other Action on the basis of a schedule. |
Auto-balancing evaluation interval | 60 minutes | Defines the time period that is used to analyze the SLAs of open Assignments. The auto-balancing engine takes into account the next three evaluation intervals to determine workload trends in a work group, and therefore to calculate the number of robots that are needed to complete existing work on time. |
Alert evaluation time | 60 minutes | By comparing the rate at which robots are processing Assignments against the Alert evaluation time, the system determines whether robots are HEALTHY or UNDERPERFORMING. |
Timeout interval for robot command to be completed | 60 seconds | The system uses this interval and the RPA service heartbeat interval to determine the timeout interval for the START command that is sent to a robot. |
Robot registration
The settings in the following tables apply to the current application:
Item | Value | Purpose |
---|---|---|
Robot | <name of Robot> | Settings define the work group assigned to a robot’s operator ID. |
Work group | <name of work group> | |
Default work group | <name of default work group> | Name of default work group |
Item | Value | Purpose |
---|---|---|
Requestor | <name of requestor> | Setting defines the default work group assigned to the robots registration operator ID. |
Work group | <name of work group> | |
Default work group |
<name of default work group> | Name of default work group. |
Item | Value | Purpose |
---|---|---|
Work group | <name of work group> | Setting defines the default Access Group assigned to the robots current work group. |
Access group | <name of Access Group> | |
Default Access Group | <name of default Access Group> | Name of default Access Group. |
Item | Value | Purpose |
---|---|---|
Dispatch operator | Robot Manager system administrator | Setting defines the List of work groups that a robot can work in, based on the registration operator that the robot registers with. This List of work groups is used when moving and scheduling robots. The robot is expected to be provisioned with all applications and credentials required to run Automations for all work groups listed. This is evaluated every time that a robot registers. |
Candidate work group list | <List of candidate work groups> | |
Default candidate work group list | List of default candidate work groups> | Default candidate work groups. |
Settings for Packages
General
Application settings | Inherited from | Value | Purpose |
---|---|---|---|
Package binary repository | Pega Robot Manager | <package binary repository> | Pega Robot Studio publishes all package binaries to Pega Robot Manager by using this repository. |
Signing and encryption
Application settings | Inherited from | Value | Purpose |
---|---|---|---|
Package Security keystore | Current application | <Package Security keystore> | Defines location of Security keystore for packages. |
Package signing auth profile | Current application | <Package signing auth profile> | Defines location of signing Authentication Profile for packages. |
Package encryption auth profile | Current application | <Package encryption auth profile> | Defines location of encryption Authentication Profile for packages. |
Assets
Application settings | Inherited from | Value | Purpose |
---|---|---|---|
Supported asset types | - | One or more <asset types> in text format, where each value is separated by a comma. | List of supported asset types. |
Settings for Usage telemetry
Usage telemetry
The Usage telemetry settings table displays the nominal number of unattended robots and attended users that are available for use in robot manager in a given year. The numbers are used to display the usage baseline in the Usage telemetry graph, which allows you to see if Pega Robot Manager is making use of the number of robots and users that you expect.
In the settings table, it is a good practice to ensure that the values in the Unattended robot count and the Attended robot count columns are up-to-date.