Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Upgrade considerations

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

When you upgrade from a previous Pega Platform version you might need to adjust the design of some sections.

If your application uses tables with personalization enabled and the users save a view, the initial grouping that you set at the design time will not be visible until a user discards the old view. You may also clean all the saved views from the database so that the new grouping appears by default.

If your application uses tables with a custom-created column toggle functionality, you need to enable the option. For more information, see Enabling the table columns visibility toggle.

If your application uses tables with custom personalization sections that include custom actions that override the standard pyGridPersonalizeActions section, change to standard personalization sections and include your custom actions in the table toolbar. For more information, see Adding custom actions to the table toolbar.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us