SR-A12522 · Issue 223510
Revised check for custom access group on post-upgrade engine start-up
Resolved in Pega Version 7.2
After upgrading through IUA on split schema, the PegaRULES engine start failed to initialize and generated an exception if the Batch Requestor Type had a custom Access Group containing certain Roles viz. PegaRULES:SysAdm4, PegaRULES:AutoTest etc.. A new API has been added to SystemSetting.java to skip this checking on security.
SR-A10306 · Issue 221964
"isAvailableSpecificDay" function updated for time zones
Resolved in Pega Version 7.2
The out-of-the-box 'isAvailableSpecificDay' function was not consistent in routing work due to time zone conversion details that resulted in incorrect decisions. To correct this, the APIs used in time zone conversions have been updated to better handle offset DateTime formats.
SR-A10683 · Issue 222397
Data transform chaining logic corrected for execution order
Resolved in Pega Version 7.2
In some cases, the execution order for super class data transforms was incorrect, causing them to run in reverse of the expected order of class inheritance. The logic for the chaining order has been updated to perform the expected sequence of executing data transform from directed inheritance and then from pattern inheritance.
SR-A14174 · Issue 227463
Improved cache clearing for AsyncServiceManager
Resolved in Pega Version 7.2
Due to changes made to the cache key pattern, the key generated to remove the ADP entry in AsyncServiceManager during request logout did not match the pattern. In some cases this led to an OOM error. The cache clearing has been updated to resolve this problem.
SR-A12864 · Issue 224900
Base64 accepts input with and without ('=') padding characters
Resolved in Pega Version 7.2
When the input given to Base64Util.decode API did not have the extra padding characters '=', the API ignored the last characters of a string with lead and trail braces ('{' and '}') when encoding and decoding and returned inaccurate results. These extra padding characters are used to complete the block structures and to maintain the correct length for the input, so logic has been added to append the remaining padding characters '=' if the input string is of incorrect length.
SR-A13449 · Issue 226932
Passivation fixed for softphone pages
Resolved in Pega Version 7.2
If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.
SR-A13449 · Issue 222715
Passivation fixed for softphone pages
Resolved in Pega Version 7.2
If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.
SR-A10527 · Issue 221023
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A10527 · Issue 221549
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A5351 · Issue 218740
Optimized Clipboard reference processing
Resolved in Pega Version 7.2
Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.