Published Release Notes

Insights from 8.5 require additional configuration after upgrade

Upgrade impact

After you upgrade Pega Platform™ version 8.5 to 8.6, the Explore Data landing page might not include insights that come from the earlier version of the product.

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

Run the pxUpgrade85Insights activity to make all insights from version 8.5 accessible for you in 8.6. By running this activity, you upgrade insights with new metadata that is required in version 8.6. For example, the pxUpgrade85Insights activity provides you with the option to set the visibility of insights to private, public or shared.

For more information about insights, see Visualizing data with insights.

Connect MQ rules configured with alias queue do not work after upgrade

Connect MQ rules that you defined with an alias queue in earlier versions of Pega Platform do not work after an upgrade to Pega Platform 8.6.

Upgrade impact

If you defined an alias queue in Connect MQ rules, after an upgrade to Pega Platform 8.6, those Connect MQ rules do not work.

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

In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values:

• "mq/pmo" = 0
• "mq/gmo" = 0
• "mq/oo_request" = 1040
• "mq/oo_response" = 16

For more information, see Creating a dynamic system setting.

Data model inheritance does not depend on ruleset context

Search and Reporting Service (SRS) in Pega Platform™ 8.6 now provides an improved method of synchronizing data model by distinct users. In applications built on earlier versions of Pega Platform, some users might encounter difficulties in indexing data. Now, the data model that the system sends to SRS does not depend on access privileges. With this enhancement, each user of your application is eligible to synchronize data.

Improved indexing of StringList and StringGroup property types

Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.

Upgrade impact

After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed. 

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

On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.

For more information, see Indexing class data.

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.