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.

Enabling security policies now requires current password

Valid from Pega Version 7.1.3

As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced.  When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.

For more details, review the Designer Studio > System > Settings > Security Policies landing page.

User Interface

Valid from Pega Version 7.1.3

Issues for cross-browser support for Designer Studio have been addressed. Improvements were made in run-time performance for data pages with grids, and a number of cosmetic changes and fixes were made.

  • Improved loading of Javascript files during saving Harness rules.
  • Login Performance improvements
  • A cursor pointer issue was addressed in Case Manager.
  • In reports, data in columns will now right-align.
  • Improved section validation functionality
  • Harnesses with screen layouts will now save when there is a refresh condition on a panel.
  • Outline View tree has been improved.
  • Improvements to Repeat Grids using Data Pages as a source.
  • Formatted text cells can be put into a grid to display the value of a property retrieved from a Report Definition join.
  • Designer Studio changes to support IE9 and IE10.
  • Improved designer studio layout
  • Designer Studio changes to support quirks mode in IE8 and IE9.
  • Improvements to SmartLabels in Data Pages
  • Tab groups will take parameters for pre-activities in a defer load setup.
  • Sections support nested dynamic layouts.

Support for OAuth 2.0 authorization code grant type

Valid from Pega Version 8.1

Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Use client-based access control to support EU GDPR requirements

Valid from Pega Version 8.1

You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.

For more information, see Client-based access control.

Archival support added to cases in Pega Cloud

Valid from Pega Version 8.1

You can now create an archival policy to move inactive cases from Pega Cloud to secondary storage. By periodically purging entries from your database, you can improve application performance.

For more information, see Case archiving.

Test ID added to repeating dynamic layouts

Valid from Pega Version 8.1

A unique Test ID property has been added to repeating dynamic layouts to support automated testing, enabling you to write dependable automated tests against any Pega application. By including this unique identifier in your automated testing, you ensure a higher level of productivity and reliability within your applications.

For more information, see Test ID and Tour ID for unique identification of UI elements.

Autogenerated controls have unique IDs

Valid from Pega Version 8.1

Autogenerated controls have a unique ID by default. This unique ID ensures that the Document Object Model (DOM) is HTML5-compliant and avoids problems that can be caused by elements having the same ID. The setting to enable or disable unique IDs is on the HTML5 Application Readiness page.

For more information, see Unique IDs in autogenerated controls.

Support for Data streaming service for Pega Cloud Marketing 7.4 applications

Valid from Pega Version 2.1

Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.

New themes in App Studio

Valid from Pega Version 8.1

New themes in App Studio determine the default colors for elements in your user interface, such as buttons and links, as well as your typography. By selecting a theme in App Studio, you can quickly apply a consistent style to your application and save development time by not having to edit the application skin in Dev Studio.

For more information, see Changing your theme.

Select or edit a label format at run time

Valid from Pega Version 8.1

At run time in App Studio, when you edit a control, you can now select a new label format for the control or edit the currently selected label format. This change provides you with the flexibility to update control labels in real time as you process cases.

For more information, see Styling controls at run time.

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