Moving Beyond Delegated Data – Meet the Records Manager Landing Page

[MarcCheong]

If you spent any time building in Pega’s Traditional UI, you are intimately familiar with how we used to handle reference data. When business users needed to manage a simple list of zip codes, product categories, or any kind of list, our go-to solution was usually to “Delegate” the Data Type.

While functional, the User Experience was notoriously clunky. Clicking a delegated data type often threw users into a rigid, spreadsheet-like interface that felt disconnected from the rest of the application. It was visually jarring, lacked modern filtering or search capabilities, and the overall UX always felt like an afterthought.

With the shift to Constellation, providing a seamless, modern experience for every part of the application is a priority. For managing data, that means leaving those old delegated screens behind.

Enter Pega Infinity '25 and the Records Manager Landing Page.

Because this is a new feature and CRUD on data awareness is still low, I wanted to break down what it is, why you should use it, and how it dramatically improves the way business admins interact with data—starting right from your initial design phase.

What is the Records Manager Landing Page?

In short, it is a specialized landing page designed specifically to manage data in a data-only context.

Instead of a disjointed, pop-up grid, the Records Manager provides an out-of-the-box, native interface to perform CRUD (Create, Read, Update, Delete) operations directly on your System of Record (SOR) data. It utilizes Constellation’s standard list UI—meaning you get powerful filtering, grouping, saving views, and search capabilities for free, all while matching the exact look and feel of your core application.

Why is this a massive upgrade?

1. Blueprint-Driven Automation & Security
The Records Manager isn’t just something you have to build manually; it comes directly from your high-fidelity Pega Blueprint. Any Data Objects you design (that contain records) are automatically added to this landing page when you generate your application.

Even better, Role-Based Access Control (RBAC) is applied automatically based on the persona access you outlined in your Blueprint. Your security model and UI are baked in from day one.

2. A First-Class Citizen UX
The biggest win for end-users is the experience. Business admins managing data no longer feel like they’ve stumbled into a developer backend. The Records Manager looks and behaves exactly like any other modern worklist or landing page in Constellation.

3. Purposeful Architecture: Cases vs. Records
In the past, developers often “hacked” together dummy Case Types just to provide a clean UI for data management, even when no actual workflow was required. The Records Manager allows you to separate simple data maintenance from complex business processes.

However, Case Types aren’t going anywhere! For updates that require a formal approval chain, a complex multi-step workflow, or a strict audit trail, a Case is still the right tool for the job. The beauty of the Records Manager is its flexibility: you can trigger simple actions or even launch a Case directly from a record on the landing page. This gives you the best of both worlds: lightweight data management for the simple stuff, and a seamless transition into a full process when the business logic demands it.

4. Lightning Fast Performance
Because the Records Manager operates in a data-only context, it bypasses the case management engine entirely for simple updates. There’s no clipboard page bloat from case instantiation, no unnecessary history tracking, and no locking overhead. It’s direct-to-database speed.

How it Works (The “Data-Only Context”)

When you trigger an action from the Records Manager (like clicking “Edit” on a row), you are operating in a data-only context.

• Forms: The UI automatically generates a Constellation-native form based on your Data Object’s fields.

• Actions: Standard Flow Actions behave differently here. Since there is no work object (pyWorkPage), you are interacting directly with the data page layer. Pro tip: Be mindful of UI refreshes and validations here, as they run directly against the data model, not a case context.

Modifying the actions

Because your high-fidelity Blueprint does the heavy lifting, import will give you a great starting point. However, if you need to adjust it manually as your application evolves, the general pattern in App Studio is:

1. Navigate to your Data Object.

2. Go to the Actions tab.

   • 

Modifying the Records Manager Landing Page

Because your high-fidelity Blueprint does the heavy lifting, your Records Manager is essentially ready to go upon import. However, if you need to adjust it manually as your application evolves, the general pattern in App Studio is:

1. Open your Channels
   • 
2. Open any of your existing Channels
3. Open your Landing pages
   • 
4. Open the Records Manager Landing Page
   • 
5. Configure your Landing Page like you would any other

Considerations:

1. The default configuration is using Insights
   • 
2. The default Insight always shows primary fields. You can not change this configuration but you can change the insight used in the tab if you want a more tailored experience.
   • 
3. The default Insight, takes from your default data source in you Settings tab of the Data Object. Upon import this is sorted by GUID, so you may want to update this to something more user friendly.
   • 

The Takeaway

The Records Manager Landing Page is the modern, Constellation-native answer to the old Traditional UI data delegation. It’s a massive quality-of-life improvement that provides business admins with a beautiful, performant tool to manage reference data—all while letting Pega Blueprint handle the setup and security automatically.

Have you had a chance to play around with this in Infinity '25 yet? Let me know in the comments what you think of the new UX compared to the old delegated rules!

Useful links and additional reads

1. Working with optional Actions in Data Objects
2. Configuring CRUD operations in Pega Platform
3. Managing operations on Data Record
4. Clearer Forms, Happier Users: Out-of-the-Box Ways to Add Context in Constellation
5. Managing data objects with nested data structures in Constellation (important DSS!)
6. CRUD Operations for Operator Records via Landing Page (Infinity '25)
7. REST CRUD actions in Constellation (Infinity '24)
8. Advanced Search – List Views vs Insights (Infinity '24)

Enjoyed this article?

See suggested articles from our Constellation 101 series and view all our Knowledge Shares from our User Experience Expert Circle.