@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.
