SR-A89757 · Issue 258597
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.
SR-A100376 · Issue 271177
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.
SR-A100376 · Issue 271369
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.
SR-A102469 · Issue 271467
Application Profile correctly updates case type description
Resolved in Pega Version 7.2.2
When creating a new application profile document, the old case type descriptions were shown instead of new updated ones; this has been corrected.
SR-A86387 · Issue 260734
Filename check updated for saving java sources to DB
Resolved in Pega Version 7.2.2
A "Problem saving Java sources to database" error was observed in the log intermittently in a system with java security enabled at web server level when there was an attempt to save assembled classes to the database with an incorrect package name (the full file path instead of com.pegarules.generated...). Before the save is done, there is a check on the package name to see whether it starts with "com.pegarules.generated" to ensure that only generated classes are saved to the database. With Java Security enabled, the system specified the entire file path as the package name and the check failed. To resolve this, the existing function has been modified to use the package name instead of the full file path.
SR-A91341 · Issue 259908
Resolved thread deadlock for AsysncServiceManager and PRHazelcastPublishService
Resolved in Pega Version 7.2.2
A deadlock was found with the locks in AsysncServiceManager and PRHazelcastPublishService where the node would receive a new message on a channel which was currently being removed. This has been fixed by updating the logic to detect and avoid locks in situations where the channel is being removed.
SR-A90203 · Issue 258113
Rule caching not disabled with BIX
Resolved in Pega Version 7.2.2
After installing AES, it was noticed that the rule cache was being disabled on any nodes running BIX. Analysis determined that the BIX extract rule was being run by an agent that calls pxExtractDataWithArgs which was turning off Rule Caching (SMA > Advanced > Rule Cache Management), and this has been fixed by modifying the BIX code to enable rule caching in this case.
SR-A92845 · Issue 260275
Rule caching not disabled with BIX
Resolved in Pega Version 7.2.2
After installing AES, it was noticed that the rule cache was being disabled on any nodes running BIX. Analysis determined that the BIX extract rule was being run by an agent that calls pxExtractDataWithArgs which was turning off Rule Caching (SMA > Advanced > Rule Cache Management), and this has been fixed by modifying the BIX code to enable rule caching in this case.
SR-A76604 · Issue 261706
Fixed corrupted reference property in column population
Resolved in Pega Version 7.2.2
After running the column population utility, the reference property information was getting corrupted. This was traced to a missing use case in the reuse and wrapping of data structures in targeted encoding, and has been fixed with improved handling for the reference marker information.
SR-A101107 · Issue 270079
TRUEFALSE function alias in report definition repaired
Resolved in Pega Version 7.2.2
After upgrade, attempting to use a Function alias with TRUEFALSE parameters in Report definition to return "false" in case the value is not set was causing a validation exception. This error was caused by a missing use case and has been fixed