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.

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.

Extended support for Dutch, Italian, and Portuguese in text analytics

Valid from Pega Version 7.2.2

The number of supported languages in the sentiment analysis feature of the Pega 7 Platform has been increased through the addition of sentiment lexicons for Dutch, Italian, and Portuguese in Text Analyzer rules. By using these lexicons, you can now determine the emotional tone of text samples that are written in these languages.

For more information, see Text Analyzer.

Free Text Model rule type name changed to Text Analyzer

Valid from Pega Version 7.2.2

The name of the Free Text Model rule type has been changed to Text Analyzer. When you upgrade to Pega 7.2.2, the rule type name of all Free Text Model rules in your application will change automatically to Text Analyzer.

For more information, see Text Analyzer.

New graphical layout and shapes on the Data Flow form

Valid from Pega Version 7.2.2

The Data Flow form has an enhanced layout that improves interaction with objects on the canvas and provides better readability of flow shapes. The enhancements also include the addition of Branch and Data Transform shapes, and the Convert shape, which supports page unpacking. With these enhancements, you can build data flows more efficiently and capture business requirements more effectively.

For more information, see Improvements to the Data Flow rule form and New shapes on the Data Flow form.

Terminate sessions for operators from outside the Pega 7 Platform

Valid from Pega Version 7.2.2

The newly added Users REST API allows an authorized administrator to terminate sessions for one or more operator IDs from outside the Pega® 7 Platform. A typical use case for this API is to terminate a user’s session when the user's security credentials, which are stored externally, are known to have changed.

Access the Pega API by clicking Resources > Pega API.

Monte Carlo data set

Valid from Pega Version 7.2.2

You can now create a Monte Carlo data set that is filled with varied and realistic-looking data. You can use this type of data set to generate random data records to test strategies and data flows.

For more information, see Creating a Monte Carlo data set record.

Support for creating PegaUnit test cases for strategy rules

Valid from Pega Version 7.2.2

You can create PegaUnit test cases for strategy rules in Designer Studio and in the decisioning user portals to compare the output of a strategy to the results that are returned by running the strategy. For example, you can verify that the number of propositions per customer is less than or equal to a certain value.

For more information, see:

Conditional filter logic supported in access control policy conditions

Valid from Pega Version 7.2.2

In the Access Control Policy Condition rule form, you can now add conditional logic that allows you to apply different access control policy conditions based on different situations, such as different types of users. The policy condition filters that are enforced  are based on the results of Access When rules. Conditional filters can be configured to allow certain highly privileged users to bypass access control security in certain situations. This is accomplished by entering an Access When but leaving the conditional logic field blank.  When such a filter is applied to a read access policy it also should be applied to the corresponding discover policy.

For more information, see Creating an access control policy condition.

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