Published Release Notes

Embedded properties in DX API v2 requests are no longer removed

In Pega Platform version 8.5, when you use the POST and PATCH v2 DX API methods with an embedded page property included in the content element of the request, the system removes all properties in the embedded page that are included in the case but are not a part of the request. Now, the merge logic has been modified to update embedded page fields sent up in the request, and keep other fields unchanged.

This feature simplifies client code and prevents data corruption.

Handlebars library update

Pega Platform version 8.6.4 uses the 4.7.7 version of the Handlebars template to generate client-side template files. The updated version, which is the latest available, introduces a wide variety of security fixes and new features that improve application reliability.

End of active support for Cosmos React version 8.6

As of the release of Pega Platform™ version 8.8 in October 2022, the early adopter Cosmos React (now Constellation) UI is no longer supported. Consequently, Pega support teams no longer accept assignments and incident reports for the 8.6 version of Cosmos React and DX SDK. Upgrade to a later version of Cosmos React or Constellation to maintain support.

Descendant class instances now included in reports

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

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.

Enhanced date circumstancing option

The date range and as-of date circumstancing features have been merged into a single feature called date circumstancing. Accordingly, the new Property and Date circumstancing option provides more flexibility when you circumstance a rule. For more information, see Specializing a rule.

Renaming a system creates the required data requestors

When you rename a system, either from the System Name landing page or by updating the prconfig.xml file, any missing data requestors are automatically created by the Pega 7 Platform. The Data Admin System Setting is also created, if it is missing.

Case Manager option for searching only attachments

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.

Configure Elasticsearch index nodes to ensure availability of index files

You can now configure Elasticsearch index host nodes in a Pega cluster outside of the Search landing page. This change ensures that search index files are always available by eliminating the need for manual configuration on the Search landing page. Use the new index.directory=<index_directory> command-line setting during JVM startup to indicate that this node is an index host node and to specify the directory where the index files will be hosted.

In addition, offline Elasticsearch index nodes can now be removed by using a new prpcUtils command-line option. For more information, see Managing Elasticsearch index host nodes outside of the Search landing page.

New Schema Tools and Query Inspector landing pages for Pega Cloud

Two landing pages have been added for advanced database administration tasks for Pega Cloud customers who use a Pega-hosted instance. These landing pages minimize the operations that need to be performed outside of the Pega 7 Platform. They are available only for customers who use a Postgres database.

From the new Schema Tools landing page, you can view PegaRULES and PegaDATA database schemas, increase the size of a column, add a composite or function index, update database statistics for a table, and defragment a table.

From the new Query Inspector landing page, you can enter an SQL query and generate an explain plan.

To use these landing pages, you must have the new PegaRULES:DatabaseAdministrator role. You access the landing pages by clicking Designer Studio > System > Database > Schema Tools or by clicking Designer Studio > System > Database > Query Inspector. The individual features that you can access are determined by the privileges that are assigned to you.

For more information, see Schema Tools and Query Inspector landing pages for tuning and maintaining databases in the Pega Cloud.