Pega Infinity 25 Constellation - Advancing User Experience and Developer Efficiency

Introduction
Pega Infinity 25 Constellation introduces a range of enhancements designed to improve usability, streamline development, and enhance the overall user experience. With smarter configuration options, modernized layouts, and improved localization, this release empowers developers to build applications faster and more efficiently while maintaining a consistent and intuitive interface.
PEGA 25 Constellation – New Features
The UI Inspector is an inbuilt out-of-the-box tool that allows developers to select and analyze user interface components directly on the screen. It provides detailed insights into their position within the UI hierarchy along with relevant metadata, making it highly effective for debugging and troubleshooting. This feature serves a similar purpose to the Live UI option in the Traditional UI, where sections could be opened and reviewed within Dev Studio.
Open the portal that you want to inspect and in the browser console from developer tools enter the following command PCore.getDebugger(). toggleInspector()
- Once this is done the application gets refreshed and an icon for the UI inspector appears to the right corner on the screen.
- Click on the UI Inspector icon and click on the component on the screen that you want to analyze or debug.
- You can have quick info of the field or can view the field meta data
- Views can be opened in Dev studio now using UI Inspector. This will help developers to debug and develop with fast pace without switching between App and Dev Studio.
Table and List View Improvements
- Auto sizing in table cells now respects the predefined maximum width of the column.
- In a list view table, set the width of the column to a certain size (ex: 100px)
- If a column’s data is too long, it’ll stop expanding beyond the configured max width and instead truncate (with ellipsis) or wrap text, depending on the column configuration.
- Label and Case IDs appear as links in timelines. (This was available in 24.1 as well)
- List Views configured as galleries now display Stage and Case-wide Actions
- Tooltips are now displayed if the header of a column is ellipse. Hover on the header column to get the full label name.
- All buttons in the table now use the secondary variant.
- In Constellation UI (the modern UI architecture in Pega), components like buttons, links, fields, etc. follow a design system that defines their visual variants — for example, primary, secondary, etc.
- All buttons that appear within a table (or list view) will now automatically use the “secondary” button style variant.
- When using Primary Fields View in a list View, the Case ID and label fields are now displayed as links.
- Custom DX components can now be added as table columns. Previously, this action required you to manually edit the View JSON, which was not a recommended best practice and of course was a tedious work.
In the above screenshot, you will be able to add an “Row Action Modal” custom dx component as a column to open the user details in a modal window on click of a link.
There is a still a limitation that, we cannot show icons and buttons as actionable items. Only images and links are possible. Hope this will be addressed in future versions.
Form Refresh Supports Page List Properties
The form refresh settings in Constellation Flow Actions now support referencing page list properties with a specific row value, such as “.myPagelist(1).scalarProp”. This enhancement significantly improves the developer experience by broadening the range of available Flow Action configuration options and providing greater flexibility in defining form behaviors.
At present, Flow Action form refresh settings do not support open-valued page lists, such as .myPagelist().scalarProp.
However, it’s still not a full-fledged feature where we can have a dynamic index for a page list. Only the specific index row property will be enabled for refresh settings making it hard to utilize this feature for dynamic tables.
Embedded Data Tables Support Views or Actions
Embedded data tables with editable modal dialog box now support Actions as source because User Actions support pre- and post-processing and refresh condition, when you use them in an embedded table, you can define validations that can help your users avoid inputting incorrect data.
User Actions - The option to use Actions is the only available option for all new tables or all newly defined modals. User Actions or Flow Actions support pre- and post-processing and refresh conditions. Consequently, when you use them to source the modal dialog box, you can define validations that can help your users avoid inputting incorrect data. When configuring an Action as a source, you can use any Action in the same class as the Data Object, irrespective of the defined actions on the Action tab of the Data Object.
As the user actions can have a pre/post DT configured, along with any input validations if required, below is an example of a simple input validation on the field Passenger Name to check the user entered value is in the predefined list of passengers.
When the user gives an input for the Passenger Name on the UI while adding the passenger info in the embedded data field, upon submitting the validation is triggered and the resultant error message is as below.
This is very good enhancement w.r.t modal window processing where pre and post processing would be possible now.
Updated Landing Pages
The updated layout type now includes support for dynamic layouts, enabling users to drag and resize interface components such as views and widgets. This enhancement reduces the dependency on column-based structures for displaying components and allows for a more flexible and adaptive interface design.
Components can be easily arranged either horizontally or vertically, depending on the nature of the data and the desired presentation on the screen.
For instance, a landing page can be configured to display insights from data objects, presenting counts and related information in a horizontal alignment using the dynamic layout capability.
As observed above, the configured layout displays the count along with corresponding information from the Data object in the proportional columns as configured. This feature would help us setting up custom size and alignment for various reporting blocks minimizing the unnecessary empty spaces.
Dynamic Text Rules
Dynamic Text Rules are highly reusable configuration components within Pega Constellation, designed to streamline communication and ensure consistency across the entire case lifecycle. They allow developers and designers to define standardized instructions that can be automatically displayed throughout various stages of a process, reducing repetitive configuration efforts and improving overall application maintainability.
In addition to standardization, Dynamic Text Rules provide powerful personalization capabilities. They can dynamically adapt content based on user inputs or case data, enabling the system to present context-specific and meaningful instructions to users. This level of customization enhances user engagement and improves data accuracy by offering clear, relevant guidance at every interaction point.
For instance, within the Initiation stage of a process, a Dynamic Text Rule can be configured at the view level to display personalized instructions using real-time data such as a passenger’s name or booking details. By leveraging this feature, organizations can create intelligent, user-focused interfaces that improve both efficiency and user experience while maintaining brand consistency across the application.
The instruction can be made as a reusable component by creating a rule and sourcing the same from the library as shown below.
Once the instruction is configured as soon as the user enters the passenger's name upon submitting, the instruction is displayed with the passenger's name in the next step.
Constellation Application Localization Now Uses a Single Locale File
Constellation application localization now uses a single unified locale file. Previously, separate language files were generated for each View, Case Type, and component, making localization more complex. With this update, a single consolidated file containing all translated strings is created and loaded once for the entire application, improving performance and simplifying management.
Below is an example of single, unified bundle of translated strings where localization is applied on different fields in views
Below is an example.
Reference Fields Support Cards
Reference fields can now be configured to appear as a gallery of single- or multi-select cards. Because cards support a combination of text fields and images, they are especially useful in situations where the user needs to compare options to make a selection.
Field Warnings and Contextual Messages in Forms
Form Views now have the capability to display contextual and informative messages alongside individual fields, providing users with real-time feedback as they complete forms. These messages can be configured using When Rules and custom logic to dynamically respond to user input. Additionally, they can be combined with Dynamic Text Rules to personalize the content based on specific field values.
This enhancement significantly improves the quality and accuracy of data collected during case processing by guiding users through form completion and reducing the likelihood of input errors or ambiguities. It enhances the overall user experience while ensuring data integrity and operational efficiency.
Simplified Case View for self-service Portals
A self-service portal serves as an intuitive user interface that empowers end users, such as customers or employees, to interact with an application independently, without requiring assistance from agents or administrators. It enables users to perform routine activities efficiently, including creating cases, tracking status updates, modifying information, and submitting requests through a streamlined and guided experience.
With the latest enhancement, developers can now design a simplified Case View specifically for self-service portals by selectively hiding components from the standard Case View. This ensures that self-service users view only the most relevant information and actions, while work portal users retain access to the complete set of case functionalities.
Configuration for the self-service Case View can be managed from the Full Page View section within the UX tab of a case type. By default, the self-service Case View mirrors the standard Case View; however, developers can easily deselect unnecessary interface elements to tailor the experience for self-service users.
New Theme Editor in App Studio
The App Studio theme designer in the Settings menu has been updated to include additional settings governing configurations such as the use of white space, background images and gradients, as well as a more granular control over colours in the theme.
The theme designer has been updated to give more control over the theme at every step of the development process.
The new brand colour setting quickly builds theme around a main colour which is useful for prototyping.
Main styles of the theme can be defined on the Quick Settings tab. And the colors tab holds the list of all colour tokens of the page and gives granular control over the theme, supporting gradients, custom fonts and images.
The changes to themes in constellation also include a new default theme Bootes that introduces a new colour scheme and stripe tables for more legibility.
Text Wrapping in Tables
Constellation tables now support text wrapping. When turned on, the Enable text wrapping action moves the text of long table entries to the next line if the string reaches the column margin.
When the Disable word wrap icon is clicked the data on the table will not be wrapped.
When Enable word wrap icon is clicked the data on the table will be wrapped.
Embedded Data Lists Support Custom Labels
You can now change the text that appears next to the Add button when adding new items in an Embedded Data list. By default, the button shows the name of the Data Object, but you can edit it just like a normal field label. This lets you use different labels for different fields that come from the same Data Object, making the interface clearer and easier to understand
Dev Studio Support for Creating and Editing Constellation Views
Dev Studio now supports the creation and editing of Constellation Views, making it possible to work with Views without having to use the Case Designer. This change supports the developer experience by reducing context switching and allowing more granular Rule management
New Reuse Library Tab for Dx Components
The Reuse Library lists assets that are available in your built-on applications stack and your current application. The Reuse Library in App Studio now includes a DX Components tab for managing DX components that extend and customize the Constellation user experience. As with other assets in the Reuse Library, such as Case Types, Data Objects, and Business Logic, DX components are displayed on the tab as tiles, to make it easier for you to recognize which ones have been added to an application already, and which ones are available to be added
New Case Hierarchy Widget
The new Case Hierarchy Widget is now available for integration within the Constellation utilities pane. This widget provides a clear and structured visualization of parent and child case relationships in an expandable nested format. Introduced in Pega Infinity 25, it enables users to seamlessly explore, preview, and open related cases, ranging from grandparent to grandchild directly within the active case environment. The widget can be conveniently positioned either in the Utility panel or as a dedicated Case tab, offering flexibility in layout and accessibility
Key Benefits
- Enables one-click navigation across related work items.
- Allows users to preview or open cases without disrupting their current workflow.
- Offers flexible placement options within the Utility panel or a specific Case tab for enhanced usability.
Configuration Steps (App Studio — Constellation)
1) Open your Case type in App Studio → UX.
2) In Full Page View, decide placement: Utility panel (right-side pane) or Case tab (new tab in the case header).
- a) From Utilities section:
- i) Add the widget by searching and selecting Case hierarchy in the widget list.
- b) From Tabs section: Add a new view under Tab, set a Name and click on submit. Click on the view name, and add the Case Hierarchy widget under Region A.
Validate by first creating a child case within your parent case and then opening the utility or case tab on parent case full view.
Support for Resizing the Case Preview
The Case Preview section can now be resized according to user preference, allowing greater flexibility when viewing it alongside other screen components. Previously, the Case Preview maintained a fixed width that could not be modified. This enhancement improves usability by enabling users to customize their workspace for better visibility and efficiency.
You can either click and drag on the edges or click the tab button on keyboard to resize the preview
Support for Resizing the Case Preview
The Case Preview section can now be resized according to user preference, allowing greater flexibility when viewing it alongside other screen components. Previously, the Case Preview maintained a fixed width that could not be modified. This enhancement improves usability by enabling users to customize their workspace for better visibility and efficiency.
You can either click and drag on the edges or click the tab button on keyboard to resize the preview
Updated Routing Table
The pyRoutingTable rule in the application now includes a new field called pySemanticKey, which stores a unique route key for each landing page. When a new landing page is created, the system automatically generates a route key derived from the page name, such as my-cases, and incorporates it into the page URL, for example, https://<hostaddress>/app/my-cases.
This enhancement ensures that each landing page has a distinct and meaningful URL, improving navigation clarity and preventing potential conflicts between pages with similar names.
If two pages have the same name, the system adds a number at the end (for example, my-cases_1) to keep each URL unique. You can also edit the route key yourself to make the URLs clearer and more meaningful.
This update prevents URL conflicts between pages with the same name and makes navigation smoother for users.
Below are the examples
Conclusion
The new features in Pega Infinity 25 Constellation strengthen the platform’s commitment to innovation and efficiency. By enabling greater flexibility, better performance, and a more engaging user experience, this update equips organizations to deliver smarter and more seamless digital solutions.
The Future of Commerce Cloud-Intelligent Automation as the New Differentiator
Manufacturing 4.0 – Smart Factories and Resilience
Smart Government – Building Digital States that Citizens Trust
Recent News
The Future of Commerce Cloud-Intelligent Automation as the New Differentiator
Manufacturing 4.0 – Smart Factories and Resilience
Smart Government – Building Digital States that Citizens Trust
Telecom in the 5G Era – From Connectivity to Monetization
Banking Reinvented – Driving Compliance and Customer Growth with AI
Ready to ship this in your enterprise?
Talk to the Novitates team about what this looks like inside your Pega or Kore.ai environment.
Book a working session