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
SR-A21653 · Issue 251550
Handling added for MasterForRequestors Null Pointer Error
Resolved in Pega Version 7.2.2
After upgrade, exceptions were being generated whenever a user logged into system. This was traced to an issue with a read-only data page being improperly passivated and ending up in the Thread level pages directory, which then caused the Null Pointer Error due to the system not finding a Thread relating to it. As an immediate fix, handling has been added for the Null Pointer Error related to the missing Thread.
SR-A21653 · Issue 255545
Handling added for MasterForRequestors Null Pointer Error
Resolved in Pega Version 7.2.2
After upgrade, exceptions were being generated whenever a user logged into system. This was traced to an issue with a read-only data page being improperly passivated and ending up in the Thread level pages directory, which then caused the Null Pointer Error due to the system not finding a Thread relating to it. As an immediate fix, handling has been added for the Null Pointer Error related to the missing Thread.
SR-A82337 · Issue 256391
Optimized properties populated in exposed columns
Resolved in Pega Version 7.2.2
After using the property optimization wizard to expose a property in a higher class, the column was not populated with data for existing instances of lower classes that used that property even though the column population job ran on those classes. The column was also not populated when new instances of the lower classes were created. This was an issue where the API was using different update methods for optimized and regular properties, causing propagation problems. HandleSchemaUpdates has been modified to update the class map for all the classes mapped to the table instead of just the class name with which the API is invoked.