Pagination is not supported in Pega Constellation
We are using Pega Constellation 23, and we have a requirement to add pagination to a table list sourced from a DataPage. However, it seems that pagination is not supported in Constellation.
Is there any alternative solution to fulfill this requirement?
Pegasystems Inc.
US
InnovationTeam
SA
Thank you for your feedback. In the end, the article presents a point of view rather than a consensus. Pagination remains one of the best solutions for end users to navigate large datasets efficiently.
I believe that not offering pagination at all in Constellation can be considered a UI limitation. A more flexible approach would be to make pagination configurable, allowing developers to decide whether to use it based on their specific use case.
I hope you reconsider this decision.
ING
IN
did you find any solution to implement pagination in constellation. if so please share the approach.
NTT DATA Global Delivery Services Pvt Ltd
IN
Pagination is an effective way of presenting the data and navigating between the records. Imagine presenting few thousand records on the UI with out pagination and navigating through it.
Scrolling through the data with out pagination doesn't make the UI user friendly and this should be allowed to configure based on the use cases
Pegasystems Inc.
US
@shanmukharaos you will not click next page 20 times neither until you find the record you are looking for - you will use search and filters. There is no next page in excel and users are able to manage millions of rows.
MCM
IN
@RichardMarsot What if the service has 1000s of record and we are looking to load only 100 at a time and then on scrolling it should load rest in 100-100 more records because loading whole records at a time is causing latency and long screen load.
NTT DATA Global Delivery Services Pvt Ltd
IN
@RichardMarsot Thank you for the insight. But, comparing the data presented in a case to data in excel might not be relevant. If there is a separate landing page only to present the data, probably this analogy works.
We will also have to look at how do the users want the data to be presented. Having multiple options to present the data would be good. Even with the existing constellation offerings, users need to scroll down to load the data beyond the specified pagination.
Knowledge Expert
SE
As always it will depend on the use case. In some cases it is better to have pagination and having an option in Pega to configure the pagination behavior would make sense to me.
In our case we are not able to configure the number of visible rows and the table bottom appears below the fold. The table also has a horizontal scrollbar, making the last columns columns invisible on smaller resolutions. With the infinite scrolling it becomes difficult to locate the horizontal scrollbar at the bottom of the table to see the content in the 'hidden' columns.
I also noticed some accessibility issues when using keyboard navigation. I am not able to focus on the case id links in the table rows using the keyboard (Pega Infinity 24.2.2).
For more information about infinite scroll vs pagination, refer : https://www.nngroup.com/articles/infinite-scrolling-tips (a more reliable source for usability articles).
@BOUANENEM insight and table will use pagination under the cover to limit the load on the back-end but from an end user perpective, we are not offering pagination in Constellation UI. We believe that user should not have to page through rows of data in the table - a better experience is to use filters on column and in the table toolbar and grouping to narrow and organize the results.
The table component also supports infinite scrolling to see all the results
Here is an article that provides more detail on this decision
https://medium.com/ruwanta-on-iam/why-i-hate-pagination-on-ui-and-api-design-28742ccf503a