We have a requirement to display hierarchical embedded Page Lists in the UI with the following structure:
Page → PageList 1 → PageList 2 → PageList 3
However, implementing this directly in Pega Constellation makes the UI complex and difficult to maintain. Deeply nested Page Lists negatively impact usability, readability, and guardrail adherence.
Is there a better design approach in Constellation to present this hierarchical data in a more user‑friendly and maintainable way?
There are 3 very good articles on the topic:
You can also check out this open source DX Component, that allows another way to do this (if DX Components are an option for you)
I’d be keen to see what others in our community have done 
@Priyam i’m not sure if this is the same question as. Dynamic Tab Creation in PEGA Constellation UI - #3 by MarcCheong ?
I replied there, but sharing here if you like:
I just did a quick configuration for this, based on the data model you provided. I would say, repeating views can work, if you make them collapsible with heading (which can be dynamic, they are not in my video).
However, based on our previous discussions, i don’t think repeating views are suitable for your project. Only Tables with Modals that are Actions support pre/post processing on adding rows, which you would need to utilise to undertake other actions you need.
As Marc mentioned - the Repeating Layout handles the multi-level nodes nicely now (Inf’25 forward).
You should be aware though that the read-only mode still displays it in the old fashion:
Hi @Priyam - just to confirm the use case, so that we can think through & suggest other possible interactions to drive to best experience for the user. If I recall from our conversation last week:
I also recall that a bulk upload via Excel is not desirable. Is this correct?
Page → PageList 1 → PageList 2 → PageList 3 is a data-structure, and is already highly complex regardless of the UI which drives it.
A better option is to first focus on what you want to achieve, than think about the design. Might be that you require multiple cases, perhaps skip the fist page / pagelist all together.
We have 5 levels deep with nested structures. We’re using combination of screenflow + field group + repeating views to showcase/add the entire dataset for better readablity and user experience.
@RameshSangili - do you have a video (or even just screen shots) you could share so we can see the experience, along with a brief description of the use case? I’m curious to see how you handled this one!
