Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Published Release Notes

Find release notes for the selected Pega Version and Capability.

Browse resolved issues for Platform releases.

Descendant class instances now included in reports

Valid from Pega Version 7.2

The Report on descendant class instances option on the Data Access tab of the Report Definition rule has a new option to now include data from all descendant classes of the report's primary class. If descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.

You can select a subset of descendant classes to include or exclude by adding a filter condition on pxObjClass.

Existing reports retain the older behavior for this option after an upgrade or update. To use the new option, you must set it for each existing report. New reports created in Designer Studio and out-of-the-box Pega 7 Platform template reports from which new reports are created in the Report Browser (pyDefaultReport and pyDefaultSummaryReport) default to the new option. If you have created custom template reports for some application classes, you must change them to enable the new option in reports that are created in the Report Browser for these classes.

See Reporting on data in multiple class tables.

Report Definition query filters can search embedded properties

Valid from Pega Version 7.2

Filter conditions on Report Definition rules that query the Elasticsearch indexes can now reference embedded properties. Previously, filter conditions could reference only the top-level properties of a class. To reference an embedded property within a filter condition, specify indexes for embedded page lists and page groups, for example, Customers(1).Addresses(1).City = Boston OR Customers(1).Addresses(1).State = MA.

These indexes are ignored in the generated query, and so can potentially match any value in a page list or group. However, filter conditions that reference multiple embedded properties in the same page list or page group, as displayed above, might not be satisfied on the same page.

BIX extracts can be scheduled and run from the Pega 7 Platform by using agents

Valid from Pega Version 7.2

You can create an agent that periodically invokes the new pxExtractDataWithArgs activity to run a BIX Extract rule. The activity takes the class and extract rule name, as well as an additional input string with a list of BIX command-line parameters, as input parameters to use for the run.

Discontinued support for list view and summary view rules

Valid from Pega Version 7.2

The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.

You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.

Report Definitions can query tables in multiple schemas

Valid from Pega Version 7.2

You can create a Report Definition that queries class tables in multiple schemas in the same database. Previously, queries on tables that were mapped to PegaRULES and PegaDATA schemas could not include tables that were mapped to other schemas, because other schemas were assumed to be in a different database. The schemas to which queried class tables belong are no longer validated when you save the Report Definition, so you can now query tables in schemas other than PegaRULES and PegaDATA. However, Report Definitions that query tables that are in more than one database fail when run.

Stage-based revision and change request management enhancements

Valid from Pega Version 7.2

The revision and change request processes are based on the case management capabilities provided by the Pega 7 Platform. The customizable flows that controlled the behavior of the revision and change request management (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of the Revision and Change Request case types that govern the behavior of revision management. The change from flow-based to stage-based revision management makes the process more transparent and easier to modify.

For more information, see Stage-based revision and change request management.

Help now available for the Predictive Analytics Director (PAD) portal

Valid from Pega Version 7.2

Help topics for Predictive Analytics Director (PAD) are now available. The comprehensive PAD documentation helps you to understand how to develop and create predictive models that you can combine with other components in Decision Strategy Manager (DSM).

For more information, see Predictive Analytics Director (PAD) and Improvements to the Predictive Analytics Director (PAD) portal.

Improvements to Visual Business Director (VBD)

Valid from Pega Version 7.2

Business monitoring and reporting no longer depends on the external Visual Business Director service because VBD is now embedded in the Pega 7 Platform. You add a VBD node to the cluster to access VBD for simulations and monitoring. In addition, when you use the Google Chrome browser, VBD launches as a new HTML client that provides the visualization.

For more information, see The Visual Business Director (VBD) HTML client and Accessing Visual Business Director (VBD).

New Proposition Filter rule

Valid from Pega Version 7.2

Instances of the Proposition Filter rule allow you to define the validity, eligibility, and relevancy criteria for a set of strategy results. Proposition Filter rules improve performance of filtering propositions that are based on proposition data and customer properties. Proposition filters give more testing and debugging capabilities by offering explanation properties. They are referenced in strategies through the Filter component.

For more information, see About Proposition Filter rules and Strategy components - Arbitration.

New Text Analytics landing page

Valid from Pega Version 7.2

The Text Analytics landing page allows you to create the sentiment and classification text analysis models using a wizard. The wizard allows you to upload training data, train a model using different algorithms, analyze the accuracy of the model, and export the model. You can also create a binary rule file that contains the model and upload it as part of taxonomy or sentiment decision data.

For more information, see Text analytics functionality enhancements.

All Pega product release notes can be found on their product pages.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us