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.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

Customize your report headers

Valid from Pega Version 7.1.5

You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.

Advanced inline report filters

Valid from Pega Version 7.1.5

You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.

Access Manager portal

Valid from Pega Version 7.1.5

Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.​

New property pxCommitDateTime

Valid from Pega Version 7.1.8

A new property, pxCommitDateTime, records the time when a record or updated rule was committed to the database. This property also allows for incremental extracts when running BIX.

New property pxSaveDateTime

Valid from Pega Version 7.1.8

A new property, pxSaveDateTime, records the date and the time that an instance was saved with business changes to the database. This property is always used when an instance is saved, whether you are creating an instance or updating an existing instance. This property is not updated when an instance is moved from one system to another, and it is not updated during certain system management operations that do not change the content of the instance, such as column exposure.

Robotic Desktop Automation (RDA) support for Pega 7 applications

Valid from Pega Version 7.2.2

You can use Robotic Desktop Automation (RDA) to integrate and unify processes that run on a user's desktop to streamline work and free your staff to focus on higher-value, customer-oriented tasks. You can use automations to retrieve information from applications that run on the desktop and send them to your Pega 7 application, and you can also use automations to send information from your application to applications that run on the desktop.

In an example Call Center application, you can use an automation to retrieve information from a legacy application running on a customer service representative's (CSR) desktop and display it in your application. You can also send information that users enter in your application (for example, an address change) to an automation to update the legacy application.

​For more information, see:

New hashing algorithm for Password property types

Valid from Pega Version 7.2.2

To provide extra protection against brute-force attacks, a new hashing algorithm has been added to the Pega 7 Platform. Bcrypt is used as a default hashing algorithm for Password property types. The bcrypt key setup algorithm takes a long time to process. This means that potential attackers would have to spend a substantial amount of time testing every possible key.

For more information, see Using the bcrypt hashing algorithm for Password property types.

Discovery features for access control policies

Valid from Pega Version 7.2.2

Access control policies now support discovery features that allow end users to view limited, customizable information about class instances that fail Read policies but satisfy Discover policies. Two types of Discovery gadgets are provided, and when discovery features are enabled, a Discovery gadget is included in the Report Viewer and in search results. Developers can customize these gadgets and include them in other parts of an application user interface.

For more information, see Discovery features for access control policies.

Update and delete actions available in access control policies

Valid from Pega Version 7.2.2

Access control policies support update and delete actions on objects. These actions control which specific instances of a class can be created, updated, or deleted by an end user in a case.

For more information, see Creating an access control policy.

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