Node description cannot match application server node name
Valid from Pega Version 6.3 SP1
A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.
Pega 7 Platform startup fails with an evaluateWhen-Exception after upgrade
Valid from Pega Version Pega Platform
If the batch requestor, Data-Admin-Requestor.BATCH, does not have access to the PRPC:Agent access group, the Pega 7 Platform fails to start up after an upgrade. The checkSecurity step fails with an evaluateWhen-Exception while evaluating access to the Data-Admin-System-Settings.pzSharedTenant when rule.
To resolve this issue, follow these steps:
- On the pre-upgraded environment, grant the Data-Admin-Requestor.BATCH access to the PRPC:Agents access group. See the online help for information about granting access to access groups.
- Move the database table record that corresponds to the batch requestor type from the pr_data_admin table of the pre-upgraded environment to the pr_data_admin table on the upgraded environment. See the online help for information about moving database table records.
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.
Cannot view all custom context posts in Pulse
Valid from Pega Version 7.2
When you use Pulse in a custom context, the custom context label is displayed as plain text instead of as a link that you can click to view all posts that are associated with the custom context.
For more information about Pulse, see the help topic Pulse.
Work attachment indexing fails with IBM SDK Java 6
Valid from Pega Version 7.1.7
Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.
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.
Ignore locale settings requires refresh after server restarts
Valid from Pega Version 7.2.1
The Ignore locale check box in operator preferences is selected to display Designer Studio in U.S. English. After a server restarts, screens initially ignore this setting. When the screen is refreshed or reopened, the screen is rendered as expected.
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.