Novitates Tech is committed to shaping a digital landscape that empowers businesses globally, offering accessible transformative solutions that ignite industry-wide change. Our dedication to innovation drives us to create strategies that redefine global business operations.
Get in touch
connect@novitatestech.com
+91 929-151-6231
209 Workafella Cyber Crown, Sec-II Village, HUDA Techno Enclave, Madhapur, Telangana, India 500081
Configuration Settings in Pega Infinity 24.2.1 offer a unified framework that blends the capabilities of Application Settings, Dynamic System Settings (DSS), and custom configuration implementations. These are grouped into Configuration Sets, simplifying application behavior management and reducing development overhead.
This article explores how Configuration Sets streamline parameterization, reduce the need for custom rule overrides, and speed up time-to-market with fewer production issues.
How Does It Work?
Pega provides a dedicated landing page in App Studio for managing configuration settings. Both developers and business users can easily add, modify, and manage application configurations without needing deep technical changes.
To understand this better, let’s walk through a hands-on example.
Creating a Configuration Set
Navigate to App Studio → Create a new Configuration Set.
Assign a name based on functional context, such as:
User Configuration
Email Configuration
Each Configuration Set can hold multiple configuration items.
Adding a Configuration to a Set
Create a new configuration setting under your Configuration Set.
This configuration behaves like an Application Setting — supporting production-level control.
Once created, Pega automatically generates all the necessary rules (data pages, properties, etc.) behind the scenes.
These configurations can be used in both:
App Studio (for case types, custom conditions, UI elements)
Dev Studio (data transforms, activities, integrations, etc.)
Using Configuration in Dev Studio
To access configuration settings in Dev Studio:
Create a generic Data Page (e.g., D_Configuration) with a parameter called Setting.
This page will fetch values based on the configuration key.
The data transform should:
Accept the Setting parameter
Reference the OOTB-generated data page to retrieve the value
Set context = Default to support global access across all layers