Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Enhanced optimized tables

Valid from Pega Version 8.5

Optimized tables now come with a greater range of options, such as support for sorting and filtering cell content in embedded sections. The new options also include passing parameter values from a data page to a table instead of manually entering the values for each of the parameters. For example, you can mark an organization name as a parameter to pass into a table. The new enhancements facilitate the transition to the more efficient optimized tables, and save time and effort.

For more information, see Optimizing table code.

Business logic-based routing cards enhancements

Valid from Pega Version 8.5

To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.

For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.

Improved support for working with cases in multiple browser tabs

Valid from Pega Version 8.5

The Cosmos design system now provides enhanced support for opening and working on cases in multiple browser tabs. Cases that users open in new browser tabs are processed independently and include the portal’s main navigation bar, which allows users to conveniently browse other pages on any tab.

Improved identification and handling of code assembly errors

Valid from Pega Version 8.5

Code assembly error logs are now more meaningful and help you identify root causes with better accuracy. Pega Platform™ now also invalidates erroneous assembly to facilitate successful reassembly when the code is accessed again. For example, if a section is not correctly assembled when a user first signs in to the system, the application attempts to reassemble that section the next time a user signs in. In this way, you can avoid lingering issues and improve stability.

Retention of mashup state on browser refresh

Valid from Pega Version 8.5

Mashup configuration now includes an option to retain the state of the mashup after the user refreshes the browser that displays the mashup. In previous releases, when users refreshed a browser window with a case in a mashup, the system discarded the state of the case and then created a new case. Now, you can enable the mashup to use the values in the Clipboard tool from before the refresh. This enhancement helps users seamlessly continue their work after a browser refresh.

For more information, see Pega web mashups for embedding Pega Platform UI in external web pages.

Custom DX API attributes for auto-generated controls

Valid from Pega Version 8.5

Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.

For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.

Tamper-proof Pega Web Mashup loading

Valid from Pega Version 8.5

To protect your application from hackers, Pega Web Mashup is now loaded in a more secure way. The system generates a channel ID in the mashup code for validation on the server, before passing the mashup request. 

For more information, see Creating a mashup.

Upgrade impact

After an upgrade to Pega Platform 8.5, existing mashups, which do not have the channel ID parameter in their code, cannot load and users see the access control warning.

What steps are required to update the application to be compatible with this change?

If you need to maintain full availability of the mashup during the upgrade of the production environment, perform the steps in Migrating existing mashups.

Support for React-based components in Pega Infinity applications

Valid from Pega Version 8.5

React-based components can now conveniently be enabled in any existing Pega Infinity™ application without the need to migrate the application to the full React UI. By selecting a single option, you can enable and experience some of the most modern functionalities, such as intuitive and comfortable landing page authoring, or the more efficient React-based tables.

 

For more information, see Enabling Cosmos React UI for landing pages.

Better support for custom PDF fonts

Valid from Pega Version 8.5

Pega Platform™ now supports loading custom fonts for PDF files from a binary file by using the CSS @font-face rule. With this enhancement, your application can generate PDF files that use custom fonts without relying on a dedicated font folder or a cloud bundle. As Pega moves away from folder-based solutions, you can migrate font management to a binary rule for quicker development and improved maintenance.

For more information, see Generating PDFs from your UI.

Optimized data schema upgrade

Valid from Pega Version 8.5

Several improvements have been made to optimize the speed of the data schema upgrade to help you experience minimal downtime during upgrade to Pega Platform 8.5™. The data schema upgrade process optimizations include the following improvements:

  • Optimized database index creation during upgrade
  • Optimized synchronization process to detect duplicate rules during the application import process
  • A new upgrade setting for Pega Cloud® Services operators that reduces the time to upgrade clients that run large Pega applications, such as the CRM Suite

For more information, see Limit upgrade downtime with data schema upgrade improvements (8.5).

 

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