Changing settings from the Pega Robot Manager interface
Edit multiple settings relating to robot registration, reporting, and configuration from the Pega Robot Manager user interface.
Robot registration – Create application-specific copies of decision tables, change the values in application-specific decision tables, or revert to inherited decision tables by removing their application-specific copies.
Reporting – Enable or disable usage data aggregation time intervals (hourly, daily, monthly, or yearly) per application or use the settings inherited from the built-on application.
For more information about reporting in Pega Robot Manager, see Reporting in Pega Robot Manager.
Configuration:
- Intervals (global settings) – Set custom heartbeat and work polling intervals.
- Thresholds by notification time – Set application-specific threshold values for various notifications for the web gadget or email.
- Settings inheritance through the application stack
By default, the decision tables and notification thresholds settings are inherited from the built-on (parent) application. If the built-on application inherits the settings from its parent application, the application stack is followed until the dependency is resolved. If no application contains its own instance of the settings, the default Pega Robot Manager settings are used.
- Creating application-specific copy of decision tables
You can create application-specific copies of decision tables, and then customize them for your application.
- Changing the values in application-specific decision tables
By using application-specific copies of settings, you can customize them without affecting the built-on application. However, the changes are also reflected in all child applications that inherit these settings from the current application.
- Setting the data aggregation interval for reporting
You can aggregate and store data in the hourly, daily, monthly and yearly intervals based on your reporting needs and database storage.
- Reverting to inherited decision tables
You can revert to inherited settings by removing your application-specific copies of decision tables. This change also affects applications that inherit from the current application.
Previous topic Assign to Robot Queue Next topic Settings inheritance through the application stack