SR-A11353 · Issue 222230
Thread cleanup added for Async declarative requests
Resolved in Pega Version 7.2
Requestors in the declarative Async Service requestor pool were growing in size over accumulated requests and were not reinitialized as would typically be expected of a resource/connection pool once the requestor goes idle. This was an issue with the Async service pool requestors not being cleaned properly and holding some page references if they used requestor level data pages with keyed parameters loaded inside the declarative requestor pool. This has been fixed.
SR-A12056 · Issue 223829
Removed paging limit on pxGetDefinitionsForTemplate
Resolved in Pega Version 7.2
In installations having more than 50 circumstance definitions associated with a number of section rules, using pxGetDefinitionsForTemplate in the report definition caused only the first 50 definitions to be visible. pxGetDefinitionsForTemplate was a final rule with a max page size of 50, and this paging limit has now been removed.
SR-A11311 · Issue 224049
StackOverflow resolved for property type conflicts
Resolved in Pega Version 7.2
Running the Repair order process was creating StackOverflow errors due to auto populate properties changing page class to subclass. This was traced to the subclass where the property was defined as a normal page list property but in the parent class was defined as an auto populate property. That caused the value for "Retrieve each page separately" to be returned as false (as sub class had this property overridden) and led to the code entering the wrong flow and creating an infinite loop in method calls. To correct this, changes have been made to the clipboard cache.
SR-A9225 · Issue 222951
Long word break added to SMA tables
Resolved in Pega Version 7.2
In Microsoft Internet Explorer 11, the SMA system management screen (the screen right after login) would sometimes not display the relevant fields in the tables until the horizontal scrollbar was moved all the way to the right. This was different behavior than with other versions of Microsoft Internet Explorer , and occurred when the content of a table-cell included a very long value without any word break. In this case, current style control could not break the long wording out to pieces, resulting in it crossing over the whole screen until the word was displayed. This was a cosmetic issue that did not influence operations, but style control has been added to enforce long word break in these cases.
SR-A12000 · Issue 222604
Check added to handle IndexOutOfBound in DirectStreamContainer
Resolved in Pega Version 7.2
An empty string passed to DirectStreamContainer.getAttribute(String, String) was resulting in an IndexOutOfBound exception. A check has been added to avoid this condition.
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.