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.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

Column Populator utility documentation out of date for prior versions

Valid from Pega Version 7.2

The documentation for using the Column Populator utility to populate newly exposed database columns is out of date for Pega 7 Platform versions prior to 7.2. For all Pega 7 versions, refer to the Pega 7.2 help documentation for instructions about how to use this utility.

Child case queries performance can be slow

Valid from Pega Version 7.2

Some customers have reported that performance is slow when they execute queries on child cases. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.

See Performance improvements for child case queries.

High number of busy waits when using Oracle SecureFiles

Valid from Pega Version 7.2.1

You might experience a high number of buffer busy waits when using Oracle SecureFiles for BLOB storage. An Oracle buffer busy wait occurs when a session cannot access a database block in the buffer cache, because another session is either reading the block into the buffer or changing the buffer. As a best practice, use Oracle 11.2.0.4 or later, because earlier versions have more problems with SecureFiles. In addition, to minimize the number of busy waits, set the hidden Oracle parameter _securefiles_concurrency_estimate to 50, and partition the table by using a composite range hash partition that is based on the pxCreateDateTime and pzInskey columns.

For more information, see Troubleshooting: High number of busy waits when using Oracle SecureFiles.

Email approval and instantiation not supported on multitenant systems

Valid from Pega Version 7.2.1

The Enable email approval check box appears on the General tab of an approval step in Case Designer in multitenant systems. It also appears on the Approval shape in Designer Studio. In addition, in Designer Studio, the Settings tab in Case Designer displays the option to configure email instantiation. However, because configuring email listeners is not supported on multitenant systems, you cannot enable email approval or email instantiation.

Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules

Valid from Pega Version 7.2

Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:

  • The upgrade fails with the following error message:
    Verify ML Readiness
  • The upgrade succeeds, but you might be unable to open changed rule forms.

If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.

This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.

MBean Javadocs download file

Valid from Pega Version 7.2.1

The Pega 7 Platform MBean Javadocs are no longer provided in the distribution image; however, you can download the MBeanJMXJavadoc.zip file that was previously provided in the distribution image.

You can also use JConsole, which is included with the Java Development Kit (JDK), to obtain MBean information. The JConsole MBean tab provides attributes, operations, notifications, and other information on all the MBeans that are registered with the MBean server.

Extract marker file not created at startup

Valid from Pega Version 7.2.1

The extract marker file (PegaRULES_Extract_Marker.txt) is not created at startup, because the rule utility libraries no longer need it. If you used to use the extract marker file to clear the static content file-based cache, to look up lists, or to control starting activities with web nodes, you can delete the contents of the PegaRULES temporary directory instead.

Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema

Valid from Pega Version 7.2.1

If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.

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