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.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

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.

Restricted SMA access

Valid from Pega Version 7.1.5

System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:

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.

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.

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.

Primary key constraint error when using JBoss

Valid from Pega Version 7.1.9

A primary key constraint violation exception might occur in the following situation: you use JBoss EAP 6.4 and SQL Server 2012 with a JDBC 4 driver, and you use two or more file listeners or JMS MDB listeners with concurrent threads that create work objects that use multiple files. If a primary key constraint violation exception occurs in this situation, update the data source configuration file to set the jta parameter to true. For example, set <datasource jta="true" jndi-name-"java:/jdbc/PegaRULES>.

Unable to create text analytics models when Java 2 Security is enabled

Valid from Pega Version 7.3

Security exceptions that prevent you from creating text analytics models are caused by the Java 2 Security feature that is enabled at the JVM level. This feature denies access to the text analytics resources that are required for text parsing functions.

Creating a text analytics model results in a failure because of a number of security-related exceptions, for example:

java.security.AccessControlException: Access denied ("java.lang.RuntimePermission""createSecurityManager")

The suggested approach for avoiding this problem is to use the text analytics models that are provided by default, for example, pySentimentModels, pyTelecomTaxonomy, and so on.

For more information, see Text Analyzer.

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