Question
Government Offices of Sweden
SE
Last activity: 21 Aug 2025 7:26 EDT
Enable pagination for archived pipelines to improve load time
Subject: Request: Pagination for Archived Pipelines Landing Page to Improve Performance
Hi Pega Support, We would like to request your assistance in improving the performance of the archived pipelines landing page.
Background
With each release, or when exceeding a patch version, clients increase the minor version. Major version upgrades ("skimming") are performed as needed. To maintain clarity and manageability, deployment pipelines are often separated for each application. Some pipelines are triggered automatically for deployment to test environments after code review and merge. This setup is just one reason for separating pipelines by application and by specific version.
As a result, many organizations end up with a large number of distinct pipelines. For every minor version (including relevant patches), a new pipeline is created. When a pipeline is no longer required, it is typically archived in order to retain its history and settings for future reference.
Current Challenge
Subject: Request: Pagination for Archived Pipelines Landing Page to Improve Performance
Hi Pega Support, We would like to request your assistance in improving the performance of the archived pipelines landing page.
Background
With each release, or when exceeding a patch version, clients increase the minor version. Major version upgrades ("skimming") are performed as needed. To maintain clarity and manageability, deployment pipelines are often separated for each application. Some pipelines are triggered automatically for deployment to test environments after code review and merge. This setup is just one reason for separating pipelines by application and by specific version.
As a result, many organizations end up with a large number of distinct pipelines. For every minor version (including relevant patches), a new pipeline is created. When a pipeline is no longer required, it is typically archived in order to retain its history and settings for future reference.
Current Challenge
In practice, the number of archived pipelines can easily exceed 500. When viewing the "Archived Pipelines" landing page, load times can exceed five minutes. Testing has shown that editing the PipelinesList section (in PegaDevOps-UI-PipelineLanding) and adding pagination to the table (when "archived") significantly improves load times (see attached screenshot.) However, as this is a final rule, the change cannot be made directly by clients.
This was noticed in Pega Deployment Manager 5.6.4.
Request
Could you please help optimize the landing page load times by enabling pagination for archived pipelines? Assistance in implementing this, or recommendations for alternative solutions, would be greatly appreciated.
Thank you for your support! Best regards, Oskar
HCA Healthcare
US
don’t load the whole Archived list on open switch that tab to defer load or load-on-expand so the page renders fast. Next, create a small custom landing page that shows only archived pipelines and uses real pagination (25–50 rows per page) via a data page or report with paging; add search and sort to cut the result set. If the list is fed by a REST service, pass page and pageSize so paging is server-side, not just in the UI. If Deployment Manager exposes a page-size setting (DSS/when rule), cap it and keep the UI page size modest. Add simple filters (application, major/minor, status) to avoid pulling thousands of rows. Because PipelinesList in PegaDevOps-UI is final, log an SR for a hotfix that either enables pagination on the OOTB section or provides an extension point; also confirm if a newer DM build already includes this. As hygiene, apply a retention policy (export or purge very old pipelines) to keep the archive lean. Finally, test with a large dataset to confirm load drops from minutes to seconds and that actions on paged rows still work.
Updated: 21 Aug 2025 7:26 EDT
Government Offices of Sweden
SE
Thank you @Sairohith
Unfortunately, it is not a tab; it's a text property with two possible prompt values (“Active” and “Archived”) that loads the section. It is located in the same section as shown in the previous screenshot.
However, it might be possible to use a Declare OnChange rule to monitor that property and load an archival section in a more effective way.
Still, we would encounter the challenge of the overlaying sections being Final, making it difficult to display this new section.
I agree that opening an SR with Pega to request a fix for the Final rule, would be a better solution for this issue.