We have been asked to maintain reference data types in a delegated manner so that they can be managed and updated directly by end users.
In the application we are developing there are 6 modules with each module containing a landing page in the system.
A module contains 1-3 case types and 1-2 landing pages.
There will be around 5-8 data types under the each module that need to be maintained — supporting the basic CRUD operations (Create, Read, Update, Delete).Business would like to maintain related data types for one module separate to data types for a different module if we can allow an experience which is intuitive and usable.
Could you please confirm the closest design pattern or recommended approach available in Pega Constellation to achieve this kind of functionality? .
@Salil one of my favourite topics! Delegated data in UI Kit wasn’t the greatest UX, Constellation has made this so much better.
So my starting point for this would be Blueprint for inspiration. When you import a blueprint to create a new application, you get a “Records Manager” landing page.
This provides a landing page, using a tabbed layout, to show each data object with CRUD actions included.
Maintaining Related Data Types
In your scenario, you want some sort of grouping so people don’t mix and match the data types. So for that, I would explore these options, and see which the users likes most:
Have multiple landing pages, designed around your features. “Feature 1 Admin” page, for example (i’m sure you have a better name). On that landing page you could follow the same Blueprint pattern above, with a few tabs for each data object.
Have a single landing page, like Blueprint does, but in each tab you could group your features. “Feature 1 Admin” tab, for example. Within each tab, you could have a few data objects to administer. I don’t personally like this, if the lists are long, could get easy to get confused and miss there is another object to administer.
The actual configuration, landing page with multiple tabs + CRUD on data objects (add a Data Object’s List View) has been available since '23. So, you could actually configure all this yourself. I only mention Blueprint as an inspiration for configuration, not a prerequisite.
