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.
Unused agents run in background
Valid from Pega Version 7.2
The Update PegaRULES database table statistics agent and the Collect PegaRULES database blob size statistics agent have been added to support future development. These agents run in the background, but they do not do anything. You can, but do not need to, disable them from the Edit Agent Schedule landing page.
For more information, see Agent Schedule form - Completing the Schedule tab.