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 Wait shape

Valid from Pega Version 8.4

Pega Platform™ now supports the enhanced Wait shape that configures the case to wait for the resolution of all child cases instead of only the child cases of a specific type. When you set up the Wait shape to stop a case until it reaches a certain status, you can decide whether the shape considers statuses from a whole case life cycle, or only the statuses after the wait begins. The enhanced Wait shape provides you with greater control over resolution of your cases. 

For more information, see Pausing and resuming processes in cases in Dev StudioPausing and resuming processes in cases in App Studio.

Improved data page performance

Valid from Pega Version 8.4

Data pages that are sourced from report definitions now support server-side paging. This functionality optimizes the performance and memory of data pages, making them more efficient at retrieving large lists of data. In addition to getting page indicators at the top of a grid, you can sort and filter columns in a grid in conjunction with paging. If you want the system to use server-side pagination, you can also enable pagination from the Data page rule form.

For more information, see Defining data page access.

Support for the JSON Web Token Bearer grant type for accessing external APIs

Valid from Pega Version 8.4

You can now access external APIs by using the new OAuth 2.0 JSON Web Token (JWT) Bearer grant type, in an OAuth 2.0 authentication profile. To use the JWT Bearer grant type as a client assertion, source the JWT from an active SSO session, a token profile, or a property reference. You can use JWTs that you obtain during an OpenID Connect SSO in connectors, to achieve user impersonation flows, such as the On-Behalf-Of (OBO) flow. The OAuth 2.0 type authentication profile now also supports authentication of client applications by using Private Key JWTs.

Instances of the OAuth 2.0 provider are now deprecated. As a best practice, use the new, unified authentication profile configuration instead.

For more information, see Configuring an OAuth 2.0 authentication profile.

Upgrade impact

After an upgrade to Pega Platform 8.4 and later, Authentication Profiles can take advantage of the new JWT based OAuth 2.0 grant type and client authentication features. To take advantage of this and other new security features, you must update any existing Authentication Profiles formats must to use those in Pega Platform 8.4 and later.

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

Since these features are available only for profiles created in Pega Platform 8.4 and later, clients must open and then save existing 'Authentication Profile' instances to ensure that the configuration is compatible with the latest authentication formats.

Email supports Microsoft Graph

Valid from Pega Version 8.4

Email integration with Microsoft Office 365 now supports Microsoft Graph. By using Microsoft Graph, you can process inbound email more securely and avoid using less secure protocols, such as IMAP and POP3.

For more information, see Creating an email account.

Email listener enhancements for faster email processing

Valid from Pega Version 8.4

Enhanced email listeners now process more emails in less time. To increase throughput, you can configure email listeners to process several emails simultaneously, instead of one at a time.

For more information, see Creating an email listener.

Support for data page aggregation

Valid from Pega Version 8.4

You can now aggregate data from multiple sources for faster and easier implementations. With this feature, you can load data pages more easily without using an activity or data transform. 

For more information, see Creating a data page

Sign and encrypt signatures and content with additional algorithms

Valid from Pega Version 8.4

You can now authenticate using JSON Web Token (JWT) token profiles to symmetrically and asymmetrically encrypt both signatures and content. All algorithms in the Nimbus JWT library are supported, including nested tokens. Custom key identifier headers (kid) are also supported. Use token profiles to securely propagate identities and transfer data between systems.

For more information, see Creating a processing JSON Web token profile.

For more information, see Creating a generation JSON Web token profile.

Anypicker control is now available

Valid from Pega Version 8.4

The new Anypicker control displays a drop-down list of values that you can group into expandable categories for faster browsing. To save time and improve search accuracy, the Anypicker control filters the available values based on the characters that the user enters.

For more information, see Adding an Anypicker control.

Referencing Rule tool in Dev Studio

Valid from Pega Version 8.4

The Referencing Rule tool now runs in Dev Studio without the need for Adobe Flash Player. This enhancement integrates the Referencing Rule tool into your work environment, which improves productivity by reducing context switching.

For more information, see Finding rules by dependency.

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.

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