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.

Automated Unit Testing is unavailable

Valid from Pega Version 7.1.1

Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.

Starting in 7.1.6, users can access AUT features from supported browser versions of IE.

Privilege required for Recent Explorer

Valid from Pega Version 7.1.1

Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer. 

Use standard Developer portal

Valid from Pega Version 7.1.1

Customized versions of the Developer portal rely on legacy components and are not supported.

To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.

Top-level (named) pages may no longer be classless

Valid from Pega Version 7.1.1

Newly created top-level (named) pages may no longer be classless or have a blank pxObjClass property. This change can affect applications upgrading from versions prior to Pega 7 to the latest version, especially when:

  • Application logic relies on a blank value in the pxObjClass property.
  • An activity assumes a new top-level page is classless and explicitly sets pxObjClass in a Property-Set step.
  • A data transform assumes a new top-level page is classless and explicitly sets pxObjClass using a Set action.

To avoid application failures, remove or update any logic that expects a blank pxObjClass. Where possible, use the new engine API that finds a page by both name and class:

findPageWithException(PageName, ClassName);

Activities and data transforms continue to create a top-level page when one does not exist. The class name is now derived from the Pages and Classes tab.

IE8 limits expansion features

Valid from Pega Version 7.1.1

Internet Explorer 8 (IE8) does not support CSS media queries, which are used by re-expansion features in the Designer Studio. IE8 users with low screen resolution (800 x 600) and a small window size may find that the explorer area in the Designer Studio collapses but cannot re-expand. 

As a work around, access the Designer Studio from another supported browser version and use the recommended, minimum screen resolution width of 1280 pixels.

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.

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