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.

PDF/UA support

Valid from Pega Version 8.4

PDF documents that you generate in Pega Platform™ are now in PDF/UA format. This enhancement improves accessibility for users who rely on assistive technology, such as screen readers.

For more information, see Setting PDF file versions.

Upgrade impact

With an upgrade to Pega Platform 8.4 and later, the underlying PD4ML library in Pega Platform changes from v3.10 to v4.x. Following an upgrade, most standard HTML-CSS conversions to PDF work seamlessly; however, if you use the following custom coding in their application to convert HTML to PDF, you may find that PDF generation works differently than expected or no longer works:

  • Application layer Java in activities that directly link to the underlying PD4ML library
  • A Rule Utility Function
  • PD4ML tags in HTML fragments

For example, the following PD4ML proprietary CSS keywords are no longer supported in v4.x:

  • pd4ml-page-break-border-top
  • pd4ml-page-break-border-bottom

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

After you upgrade to Pega Platform 8.4 and later and find your PDF generation works differently than expected or no longer works, you should consult the latest documentation available at pd[4]ml support site. You may also consider using the Compact CSS instead of the application skin for PDF generation; for details, see Creating PDF files by using a compact style sheet.

Personalized views in table layouts

Valid from Pega Version 8.4

Table layouts now provide users with the option to save preferred run-time configurations, such as column visibility and filtering, as permanent profiles. This enhancement helps users create dedicated views for specific work scenarios, which reduces the need for repetitive adjustments to the user interface and improves productivity.

For more information, see Enabling table personalization.

Upgrade impact

After an upgrade to 8.4 and later, the default table toolbar styling and experience may be unexpectedly different for any customized tables in a client's application: if you enabled a tool bar action for a personalizable table and the 8.4 application overrides your customization, your application now displays the default 8.4 table toolbar.

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

Existing clients that upgrade to Pega Platform 8.4 and later may need to update applications in some scenarios. Any custom actions present in the overridden section may need to be re-authored into this toolbar using the additional actions section.

Flow rules not supported in IE8

Valid from Pega Version 7.1.1

In versions prior to 7.1.2, flow rules do not open in Internet Explorer 8 (IE8). Upgrade your system to the latest version of PRPC or access flows from another supported browser.

Privilege required for Recent Explorer

Valid from Pega Version 7.1.1

Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer. 

Use standard Developer portal

Valid from Pega Version 7.1.1

Customized versions of the Developer portal rely on legacy components and are not supported.

To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.

Top-level (named) pages may no longer be classless

Valid from Pega Version 7.1.1

Newly created top-level (named) pages may no longer be classless or have a blank pxObjClass property. This change can affect applications upgrading from versions prior to Pega 7 to the latest version, especially when:

  • Application logic relies on a blank value in the pxObjClass property.
  • An activity assumes a new top-level page is classless and explicitly sets pxObjClass in a Property-Set step.
  • A data transform assumes a new top-level page is classless and explicitly sets pxObjClass using a Set action.

To avoid application failures, remove or update any logic that expects a blank pxObjClass. Where possible, use the new engine API that finds a page by both name and class:

findPageWithException(PageName, ClassName);

Activities and data transforms continue to create a top-level page when one does not exist. The class name is now derived from the Pages and Classes tab.

All tabs are accessible on delegated rule forms

Valid from Pega Version 7.1.1

Delegates can now access all tabs in a delegated rule form.

You can continue to customize the development experience for delegated users, such as line managers, who may not require the full set of rule form options. For example, you can prevent users from adding new nodes on the Decision Tree form or using the expression builder on the Map Value form. All users, including delegated users, can remove these restrictions if they hold a rule-editing privilege.

For more details on this process and a list of commonly delegated rules, see How to delegate a rule.

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