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.

Naming pattern changed for file data sets

Valid from Pega Version 8.6.3

File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.

Upgrade impact

If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.

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

If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.

Application Express and the Content Security Policy

Valid from Pega Version 7.1.7

Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.

When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.

Application overlays are enhanced to include more rules types that business users can change through the Decision Manager portal

Valid from Pega Version 7.1.7

Revision management overlays have been extended to include additional rule types (decision tree, and map value), enhancing the extent to which business users can review and change the logic used in strategies. For more information on this new feature, see the Revision Management landing page.

Direct deployment of decision parameters

Valid from Pega Version 7.1.7

Direct deployment overlays now enable business users to own decision parameters. Revisions based on this new type of overlay can be directly activated by Decision Manager portal users. For more information on this feature, see the Revision Management landing page.

Predictive Analytics Director portal

Valid from Pega Version 7.1.7

Predictive Analytics Director (PAD) has been integrated into Pega7, allowing you to develop and generate predictive models that can be used in strategies and process flows. The following new rulesets have been added to PegaDM to support this functionality: PredictiveAnalytics-IntSvcs, and PredictiveAnalytics-UI. For more information on rules using models generated by the Predictive Analytics Director portal, see About Predictive Model rules.

Third party models integration made possible by directly importing PMML in predictive models

Valid from Pega Version 7.1.7

Predictive models can now import models in PMML format. The PMML integration in predictive models allows you to use third party models without extra conversion and configuration. For more information on this new feature, see About Predictive Model rules.

Improved adaptive model accuracy

Valid from Pega Version 7.1.7

Enhancements have been made in the grouping scores method that is used to create the adaptive model outcome profile (also known as: classifier). Because scores form the base for calculating propensities, these changes make models more accurate. The enhanced grouping scores method is available with any new model generated in Pega 7.1.7 and does not require any changes to existing adaptive model rules or adaptive model components. For more information on adaptive models, see About Adaptive Model rules.

In-memory Adaptive Analytics Manager process

Valid from Pega Version 7.1.7

The new internal Adaptive Analytics Manager (ADM) process running in PRPC makes it possible to use adaptive analytics without the availability of the external ADM server. Although not a replacement for the external ADM server, it streamlines the design and development of applications making use of adaptive analytics. For more information on the configuration that allows your application to use the internal ADM process, see the Infrastructure Services landing page.

Delayed adaptive learning

Valid from Pega Version 7.1.7

Data flows, a new rule type in Pega 7.1.7, allow you to store adaptive inputs and interaction results for a given period of time when running a strategy. This makes it possible to capture and learn from responses at a later date. For more information on data flow design for delayed learning, see Data Flow rule form - Completing the Data Flow tab.

Decision data stores

Valid from Pega Version 7.1.7

Decision Management in Pega 7.1.7 introduces two new concepts to manage data: decision data stores, and Data Nodes (DNodes). Horizontally scalable, and supported by DNodes, decision data stores take data from different sources, and make it available for real time and batch processing. This infrastructure is managed through the DNode Cluster Management landing page.

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