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.

Report Browser removed from Designer Studio

Valid from Pega Version 7.1.9

The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.

The Report Browser is still available in the Case Manager portal.

Enabling historical compliance score data

Valid from Pega Version 7.1.9

Project stakeholders can now track the compliance score for an application over time to better understand and manage ongoing development adherence to Pega 7 Platform guardrails. The compliance score history can be displayed on a line graph on the Compliance Score tab of the Application Guardrails landing page. The data is collected daily and displayed in weekly increments, up to four weeks prior to the current date.

For more information, see Guardrails compliance score, Enabling compliance score history, and Compliance score trend reporting.

Application Sizing Wizard worksheet template now includes business impact

Valid from Pega Version 7.1.9

A column for business impact has been added to the project sizing template used by the Application Sizing Wizard. Project owners can now incorporate this assessment into their project sizing.

New Business impact optimization dashboard

Valid from Pega Version 7.1.9

On the Analysis tab of the Application Profile landing page, you can now enable historical specification count and implementation progress by complexity and business impact. On the Business impact optimization dashboard, you can view counts of specifications by complexity and business impact. You can also view counts, by business objective, of specifications that have been implemented and for those not yet implemented. You can filter specifications by release and iteration.

For more information, see Viewing specifications by complexity, impact, and business objective, and Associating project specifications with business impact and complexity.

New field types in Form Builder

Valid from Pega Version 7.1.9

You can create forms in Form Builder that include the following field types:

  • Data reference – Prompts users with a list of data records or instances of a specific data type.
  • User reference – Prompts users to select or search for an existing user in the application.

For more information, see Data references in Form Builder and User references in Form Builder.

Reusable components in Form Builder

Valid from Pega Version 7.1.9

You can reuse an existing form or data reference when creating a form. By referencing the existing fields in your application, you save time and build forms that are easier to maintain. Refer to the Reuse fields panel in Form Builder to view all of the fields, forms, and data references in your application.

For more information, see Reuse fields panel in Form Builder.

Support for enterprise and express applications

Valid from Pega Version 7.1.9

When you run the New Application wizard, you can create two types of applications:

  • Enterprise – A full-scale application that has access to all the capabilities in the Pega 7 Platform.

    By default, enterprise applications are developed in Designer Studio, but users have access to express mode.
  • Express – A small-scale application that has access to a subset of the capabilities in the Pega 7 Platform.

    Express applications are developed in express mode, and are ideal for new users or for quickly testing functionality.

For more information, see Express applications.

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.

Case Manager option for searching only attachments

Valid from Pega Version 7.2

Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.

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