SR-A4005 · Issue 211179
Check added to pass value instead of parameter name from icon control
Resolved in Pega Version 7.2
After upgrade, an issue was found with passing a property to an activity from the deprecated icon control: instead of the value of the property, the property name itself was passed to the parameter of the DoAction activity. A check has been added to the generateButton RUF to catch property references and populate the property value at run time instead of the property name as a literal value.
SR-A6169 · Issue 204154
Corrected compilation error when using param.value in Repeat Layout label
Resolved in Pega Version 7.2
A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.
SR-A10502 · Issue 220758
Ill-formed Operator IDS auto-set to Hourly
Resolved in Pega Version 7.2
Operators with an empty license type parameter were being treated as Web based users rather than Hourly usage. This was traced to the PRPC license daemon electing to treat the usage data as Invocation usage data when a User with an ill-formed Operator ID signed into and used PRPC. This was an issue with the problematic ID causing an Empty value check in the licensetype value, and a check has been added to divert ill-formed operator IDs to hourly usage status.
SR-A5299 · Issue 217135
Resolved empty context NPE in parse clipboard activation
Resolved in Pega Version 7.2
A NPE was being generated during thread activation of some parse clipboard pages . This was traced to a wrapper command used to set special java status, and the code has been updated to ensure that the engine context is not empty in these cases.
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.