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.

Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6

Valid from Pega Version 8.6

Pega Infinity™ uses Hazelcast distributed clustering technology to share data and send events between server nodes. Beginning in Pega Infinity release 8.6, Pega Infinity supports Hazelcast 4.x.
 
Note: Note: Because Hazelcast 3.x is in extended support, upgrade to Hazelcast 4.x before the extended support period for Hazelcast 3.x ends.

Upgrade impact statement

On-premises upgrades of Pega Infinity release 8.4.2 and later to version 8.5.1 or later on Tomcat and PostgreSQL are completed with near-zero downtime. However, upgrading to Hazelcast 4.x requires that you shut down and restart your application server.

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

Hazelcast 3.x is enabled by default. For near-zero downtime upgrades, you do not need to perform any action.

For instructions about upgrading to Hazelcast 4.x, see one of the following topics:

Improved indexing of StringList and StringGroup property types

Valid from Pega Version 8.6

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.

 

End of support for Microsoft Internet Explorer 8 and quirks mode applications in Pega 7.1.9

Valid from Pega Version 7.1.9

In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 8 in January 2016, Pega 7.1.9 does not support Internet Explorer 8, nor does it support non-HTML5 standard user interfaces.

You must upgrade to Microsoft Internet Explorer 9 or later or use Google Chrome, Apple Safari, or Mozilla Firefox. If you are using Internet Explorer 9 or later, you must turn off compatibility mode by accessing the Compatibility View settings.

Note the following:

  • Pega 7.1.9 does not support user interface rules that are not based on HTML5 standards (rules in quirks mode).
  • If you use applications that are rendered in quirks mode, which enables Pega 7 to correctly display and render non-HTML5 standard user interfaces, you must update them to standards-based HTML5 user interfaces when you upgrade to Pega 7.1.9 or later. Pega 7 provides automated tools to help you migrate your applications.
  • Pegasystems Global Customer Support will not investigate or fix any Pega 7.1.9 bugs or support requests that are exclusive to Internet Explorer 8 or quirks mode user interfaces.

You can quickly identify which components of your application user interface are not HTML5 standards-based by clicking Designer Studio > User Interface > HTML5 Application Readiness.

Upgrading to Pega 7.1.9 and a newer browser offers the following benefits:

  • These browsers are HTML5 and CSS3 compliant.
  • New features are supported and existing features work as intended.
  • The Pega 7 Platform user interface is displayed and rendered as intended.
  • Browser security is enhanced.

If you have additional questions about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.

Updated default system pulse processing settings

Valid from Pega Version 7.1.9

The default settings for system pulse processing have been updated in this release.

Upgrades to Pega 7.1.9 from a previous version of the Pega 7 Platform use database pulse by default. Database pulse synchronizes rule changes at a periodic interval across all nodes in a system.

New installations of Pega 7.1.9 use cluster-based pulse by default. Cluster-based pulse immediately updates rule changes across all nodes in a system after the changes are saved.

You can change the database pulse setting to the cluster-based pulse setting by updating the value attribute for initialization/pulse/transport to "cluster" in the prconfig.xml file or in the Dynamic System Settings. Changing from database pulse to cluster-based pulse requires a full cluster restart after the changes are made.

For more information, see Pega-RULES agents.

PegaDISTRIBUTION Manager (PDM) is no longer available

Valid from Pega Version 7.1.9

The PegaDISTRIBUTION Manager (PDM) is no longer available in the Pega 7 Platform. The related PDN articles and help topics have been archived.

Rules Assembly cache is deprecated

Valid from Pega Version 7.3.1

Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.

Use of PegaRULES_Extract_Marker.txt to delete cache is deprecated

Valid from Pega Version 7.3.1

The PegaRULES_Extract_Marker.txt file is deprecated. The system uses the presence or absence of the PegaRULES_Extract_Market.txt file to determine at startup whether to delete the static content, service export, and lookup list file system-based caches. In the rare situation that you need to delete these caches manually, use the System Management Application (SMA) ETier Static Content Management page. Using SMA does not require restarting the node.

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