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.

Cassandra 3.11.3 support for Pega Platform

Valid from Pega Version 8.3

Increase your system's reliability and reduce its memory footprint by upgrading the internal Cassandra database to version 3.11.3.

For on-premises Pega Platform™ users, after you upgrade to Pega 8.3, it is recommended that you manually upgrade to Cassandra 3.11.3. You can upgrade to Cassandra 3.11.3 on all operating systems except IBM AIX. If you do not want to upgrade to Cassandra 3.11.3, you can continue to use Cassandra 2.1.20, which is still supported.

For Pega Cloud Services 2.13 and later versions, Cassandra automatically upgrades to version 3.11.3 after your environment is upgraded to Pega Platform 8.3.

For information on how to manually upgrade to Cassandra 3.11.3, see the Pega Platform 8.3 Upgrade Guide for your server and database at Deploy Pega Platform.

Upgrade impact

After an on-premises Pega Platform upgrade, you still have the older version of Cassandra and must manually upgrade.

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

To upgrade Cassandra, you must create a prconfig setting or a dynamic system setting with the new Cassandra version and then do a rolling restart of all the Decision Data Store nodes to upgrade them to the latest version of Cassandra.

 

Text analytics models editing and versioning

Valid from Pega Version 8.3

Pega Platform™ now supports editing and updating training data for text analytics models.

Pega Platform also supports the versioning of text analytics models. When you update the model, Prediction Studio creates an updated model version. You can then switch between the model versions.

Upgrade impact

In versions of Pega Platform earlier than 8.3, the training data for text models was stored in the database. In Pega Platform version 8.3 and later, the training data for text models is stored in Pega Repository. You cannot build new models without setting the repository. After the repository is set, all text models are automatically upgraded and will work normally.

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

After a successful upgrade, set the repository in Prediction Studio before building or updating any Natural Language Processing (NLP) models.  In Prediction Studio, click Settings > Text Model Data Repository.

 

For more information, see:

 

Text analytics models migration

Valid from Pega Version 8.3

Pega Platform™ now supports the exporting and importing of text analytics models. For example, you can export a model to a production system so that it can gather feedback data. You can then update the model with the collected feedback data to increase the model's accuracy.

Upgrade impact

In versions of Pega Platform earlier than 8.3, the training data for text models was stored in the database. In Pega Platform version 8.3 and later, the training data for text models is stored in Pega Repository. You cannot build new models without setting the repository. After the repository is set, all text models are automatically upgraded and will work normally.

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

After a successful upgrade, set the repository in Prediction Studio before building or updating any Natural Language Processing (NLP) models.  In Prediction Studio, click Settings > Text Model Data Repository.

 

For more information, see:

User interface distortions in the Decision Manager portal

Valid from Pega Version 7.1.6

By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.

Workaround:

  1. Open the application record.
  2. In Application Rulesets, remove UI-Kit-7.
  3. Save the application record.

User interface distortions in the Predictive Analytics Director portal

Valid from Pega Version 7.1.6

By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.

Workaround:

  1. Open the application record.
  2. In Application Rulesets, remove UI-Kit-7.
  3. Save the application record.

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