Use Case:
-
Screen 1:
The user enters a Location Count (N) and submits the screen.
-
Screen 2:
Based on the value of N, the UI dynamically renders N tabs—one tab for each location.
-
Tab Behavior:
Each tab is backed by an entry in a Page List and displays a complex repeating view sourced from the corresponding page, allowing the user to view and manage detailed location-specific data within each tab.
Please find the rough Page structure below for reference:
Each Locations Page List needs to be visible as tab so that user can easily see and maintain the details under each location. Under Unit List also we have few tables and other details so, it’s a very complex embedded requirement.
Repeating view for Locations List might an option but considering the complexity of the UI it’s very difficult for to maintain and view the details in one screen (lots of scrolling)
Requesting PEGA experts’ opinion on this requirement.
@RAHULK0923 is this the same question as posted here? UI creation with 3 level embedded Pagelist ? Though you’ve provided a little more detail about data model and seem set on tabs as the view (which is one solution).
Copy of my response from that question:
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 
@RAHULK0923 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.
3 Likes
Agreed with @MarcCheong !
We had a similar requirements with 5 level deep nested structure and we are able to achieve through Repeating views. We initially analyzed the tabs but we changed our direction to Repeating views but that offers more flexiblities for the business with field groups.. I recommend to go through Repeating View options before moving away to Dynamic tabs.
1 Like
Hi Marc, Thank you for quick response. As i mentioned in the post currently we are going with Repeating View only as this is satisfying our requirement, but we wanted to check with Experts regarding Dynamic Tab or any alternative approach that will make the UI more intuitive.
But seems like Repeating View is the only best approach if we are not going for DX component.
Thank you.
