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.

Additional upgrade scripts for new columns

Valid from Pega Version 7.1.4

In Version 6.2, additional columns (Major, Minor, and Patch) containing ruleset Version information were added to 15 tables in the PRPC database. When upgrading from a pre-Pega 7 release, scripts must be manually run after the upgrade to populate these columns.

These scripts are located in the Resource Kit, under Additional Upgrade Scripts.

  • If upgrading to a single schema, run both scripts.
  • If upgrading to a split schema, run the _data script against the data schema and run the _rules script against the rules schema.
  Depending upon your database type (platform) and the size of your database, these scripts may require significant time and system resources to run.

Choose the scripts for your database type:

  • db2zos_rulesetversion_columns_data.sql
  • db2zos_rulesetversion_columns_rules.sql

 

  • mssql_rulesetversion_columns_data.sql
  • mssql_rulesetversion_columns_rules.sql

 

  • oracle_rulesetversion_columns_data.sql
  • oracle_rulesetversion_columns_rules.sql

 

  • postgres_rulesetversion_columns_data.sql
  • postgres_rulesetversion_columns_rules.sql

 

  • udb_rulesetversion_columns_data.sql
  • udb_rulesetversion_columns_rules.sql

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.

Problem with truncating Decision Data Store data set

Valid from Pega Version 7.1.9

The Truncate operation for the Decision Data Store data set may cause timeout exceptions. This problem is caused by the Apache Cassandra database that waits until compaction tasks finish before it can truncate the data set.

Recommendation:

Repeat the Truncate operation until it is successful.

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.

Existing operator IDs during upgrades and updates

Valid from Pega Version 7.2.2

Upgrades and updates are always performed in secured mode to help prevent unauthorized access to your system. In secured mode, the administrator@pega.com operator ID is always overwritten, but other existing standard operator IDs are not modified. New operator IDs are inserted in secured mode. For more information, see the Deployment Guide for your environment.

System starts slowly after upgrade or update on IBM DB2 for z/OS

Valid from Pega Version 7.2.2

Additional tables are added to upgraded and updated systems. If your system starts up very slowly after an upgrade or update, the database statistics on these new tables might not have generated correctly. To correct this issue and improve performance, your database administrator needs to manually rebuild the statistics for all tables in the rules schema.

Clustering equal to none might cause errors

Valid from Pega Version 7.2.2

Some Pega 7 Platform features might not work when theidentification/cluster/protocolsetting in the prconfig.xml file is set to none. Some features that might not work are remote tracing and management actions on the node from the Requestor Management and Agent Management landing pages. Setting the clustering protocol to none is not recommended and will not be supported in a future Pega 7 Platform release.

Remove obsolete versions of the PredictiveAnalytics-UI and PredictiveAnalaytics-IntSvcs rulesets

Valid from Pega Version 7.2.2

After you upgrade the Pega 7 Platform to version 7.2.2, remove the PredictiveAnalytics-UI and PredictiveAnalytics-IntSvcs rulesets from your application as their versions are obsolete. Beginning with Pega 7.2.2, use the Pega-DecisionScience ruleset that contains the latest versions of the PredictiveAnalytics-UI and PredictiveAnalytics-IntSvcs rulesets.

For more information, see About ruleset versions.

Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.2

Valid from Pega Version 7.2.2

After you upgrade the Pega 7 Platform to version 7.2.2 from a version prior to 7.2,1, you need to configure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.

For more information, see Services landing page.

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