Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Settings inheritance through the application stack

Updated on November 29, 2022

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.

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

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us