The table is arguably one of the most commonly used components in applications built using Pega. It is also one of the most feature rich components. Over the years a lot of complexity has been added to the component so that it was able to fulfill requirements for which older browsers did not have standard HTML + CSS based solution. We have however deprecated older browsers, and as of the publishing of this article we only support IE11, Edge, Safari, Chrome, and Firefox, and have dropped support for older versions of Internet Explorer. That means that we can start to use some of the newer capability and advancements in both browser technology and front-end technology.
At the same time, all that functionality cannot be replaced within a matter of a release, and in certain cases there may not be good modern alternatives. Over the last few releases we have been developing a new modern table, which comes to life when the 'Optimize code' checkbox is enabled. At this time this new mode of the table contains many features and can be used in many use cases. So wherever possible we encourage you to use this new table by checking the 'Optimize code' checkbox. Here are the advantages:
Uses client-side template-based rendering technology, which is much more performant than the server-side rendering that is used by the old table
Supports new capabilities such as table personalization where an end user can personalize their view of the table by adding and removing columns, sorting and filtering the data in the table and saving that state as a personalization
We will continue to add new capability to this new rendering of the table, whether it be net new functionality or moving functionality from the old table to the new table. Once we reach a critical mass of features, the 'Optimize code' setting will be the default mode of rendering for the table, and at a point in the future we will deprecate the old rendering of the table.
Yes, Pagination is a good idea whenever there is an unknown number of rows. WIth 8.5 data pages sourced via pega data support pagination and load times are greatly improved as a result.
We have disabled Report Definion source since Data pages have been best practice for quite some time. Data pages gives you added benefits of caching on the server therefore not requiring data to be fetched on every render of the grid.
Expandable row capability is not currently part of our plan for the optimized table.
Posted: 1 year ago
Updated: 1 year ago
Posted: 9 Dec 2020 16:41 EST Updated: 9 Dec 2020 16:43 EST
Concern is that mode (optimize) not handling Custom controls. How to find which part of the custom code is causing issue and fixing it is stopping us to covert to Optimize code. The same control is working with out converting table to Optimize mode. Any suggestions?
Posted: 1 year ago
Posted: 5 May 2021 2:13 EDT
Sai kishore Kandoori (kishore1505)
Principal Application Engineer, Sales Automation
@SURENDRA Peddi Optimized table is built using Client side template based technology that we first introduced in 7.3.1. So the table can only embed other content that is also client side template based. All our OOTB controls and layouts are client-side template based. Custom controls are not, and therefore don't work within the optimized table.
Posted: 1 year ago
Posted: 10 Dec 2020 10:48 EST
Pradeep Arepally (PradeepRao)
@kamav Hi, Greetings. I am on Pega 8.7.0 and using Optimize Code for a table layout. This is good however i am trying to get Next, Previous buttons on the Modal window but is not working. If i do not have this Optimize Code, I can get these buttons on the modal window. Is there any alternative or work around to get the Next and Previous buttons in Optimize Mode configuration?