Skip to main content

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

Technical considerations for configuration sets

Updated on May 31, 2022

Configuration sets provide tools for run-time users to flexibly adjust application behavior in a no-code way. When you create configuration sets, considering crucial technical aspects can help you deliver an application that precisely targets business objectives. Additionally, configuration sets minimize custom rule overrides, so that maintaining and upgrading your application is more convenient.

Rule status

When you create a configuration, in the background the system creates a property whose value users can adjust at run time. You can also create a decision table to calculate the value automatically. When you move your application to the production environment, ensure that the rules that include configuration sets and decision tables are final. As a result, you ensure that users cannot edit the rules, and avoid future update issues caused by custom rule overrides. For more information, see Setting rule status and availability.

One configuration set per feature

For efficient and transparent organization of resources, ensure that one configuration set includes configurations that define one feature. For example, in a financial application, you can create a configuration set that gathers configurations that define the application UI, and another set for configurations related to account policies and limits. At run time, an application displays each configuration set on a separate tab. By collecting related configurations in one set, you help users quickly find the configuration that they need to edit, as in the following example:

Configuration sets at run time
Administration landing page with two configuration sets that are displayed on separate tabs

Impact of access groups on the run-time experience

An application user's access group defines the actions that the user can perform on configurations at run time in the following ways:

  • Users with the ApplicationName:Administrators access group can view, edit, and delete values for configurations.
  • Users with the ApplicationName:Managers access group can view and edit values for configurations.
  • Users with the ApplicationName:Users access group can view values for configurations.
To ensure that users can perform additional actions without modifying an access group, you can grant access to configuration sets to personas in App Studio. For more information, see Configuring access options for a persona.

The user access group also impacts the editing of decision tables at run time. Only users with the ApplicationName:Administrators access group can view and edit decision tables in the configuration sets. For users with other access roles, you must first edit their access groups by adding the PegaRULES:ViewConfigTable privilege to view decision tables, and the PegaRULES:EditConfigTable privilege to edit decision tables. For more information, see Adding a role to an access group.

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