Settings inheritance through the application stack
By default, all decision tables and notification thresholds settings are inherited from the built-on (parent) application. If the built-on application inherits those settings from its parent application, then, to resolve any dependency, the application stack is traversed until the dependency is resolved. If no application contains its own instance of the settings, the default settings for Pega Robot Manager are used.
To customize settings on an application-specific level, create an application-specific instance of the settings that you want to modify, and then edit this instance. By using application-specific copies of settings, you can customize them without affecting the built-on application.
When you edit settings in your current application, the changes are also reflected in all child applications that inherit these settings from the current application.
Previous topic Changing settings from the Pega Robot Manager interface Next topic Creating application-specific copy of decision tables