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.

New options to manage proposition validity

Valid from Pega Version 7.2.1

Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.

For more information, see Proposition validity.

BIX performance improvements for CSV output in the Pega Cloud

Valid from Pega Version 7.2.1

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

Add custom HTTP response headers in your application

Valid from Pega Version 7.2.1

The Pega 7 Platform supports the addition of custom security HTTP headers that are supported by your browser. For example, you can now create custom X-Frame-Options, X-XSS-Protection, and Strict-Transport-Security headers. These headers improve the security of your application against client-based attacks.

For more information, see Creating a custom application header

Define adaptive model context

Valid from Pega Version 7.2.1

You can define model identifiers in the Adaptive Model rule instance, which serve as partitioning keys, by selecting properties from the top-level SR class of your application. The Adaptive Decision Manager (ADM) server uses model identifiers to create adaptive models that use the same configuration, but collect different adaptive statistics. Use model identifiers in the Adaptive Model rule to create adaptive models for your purposes.

For more information, see the Context tab on the Adaptive Model form.

DSM rulesets become part of the PegaRULES application

Valid from Pega Version 7.2.1

The Pega-DecisionArchitect, Pega-DecisionEngine, Pega-BigData, and Pega-NLP rulesets were moved from the PegaDM application record to the PegaRULES application record. This change makes decision management functionality available for Pega 7 Platform users by default without any additional configuration required.

For more information, see DSM rulesets become part of the PegaRULES application.

HDFS data sets support Parquet files

Valid from Pega Version 7.2.1

The Parquet file format has been added to the list of supported file formats for data storage in the Hadoop Distributed File System (HDFS) data set record. On the Pega 7 Platform, you can now access an HDFS data set that stores data in the Parquet file format and perform various operations on that data set.

For more information, see Big Data enhancements in decision management.

New rule type: External Data Flow

Valid from Pega Version 7.2.1

You can now create External Data Flow rules on the Pega 7 Platform. By using this rule type, you run predictive models outside of the Pega 7 Platform and directly in the external Hadoop data set infrastructure. Processing large amounts of data on an external infrastructure improves overall performance on the Pega 7 Platform by reducing data transfer between the Hadoop cluster and the platform.

For more information, see Big Data enhancements in decision management.

New graphical framework for the Event Strategy rule form

Valid from Pega Version 7.2.1

The Event Strategy rule form introduces a new graphical framework that includes redesigned strategy shapes, improved navigation, and faster response time when building a strategy. These changes contribute to creating a more functional and engaging environment that allows strategy designers to successfully develop and maintain event strategy rules.

For more information, see Event Strategy rule type enhancements.

New shapes in the Event Strategy rule type

Valid from Pega Version 7.2.1

The Event Strategy rule type supports branching and merging of the data stream by using the new Split and Split and Join strategy shapes. You can now split your event strategy into several paths to identify multiple types of events with a single rule instance.

In addition, the Lookup shape replaces the Static Data shape. You can add static data anywhere in the strategy. For example, you can filter out irrelevant events, and then evoke static data for only the events that are relevant to the strategy.

For more information, see Event Strategy rule type enhancements.

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