SR-A12450 · Issue 223679
Trailing line removed from breadcrumb
Resolved in Pega Version 7.2
When creating a work item, the breadcrumb showed a trailing line when it displayed "Review and Confirm". This was an issue with a page change class in middle of a screenflow, and has been fixed.
SR-A12537 · Issue 224734
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A13730 · Issue 226426
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
SR-A6996 · Issue 215315
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
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-A7649 · Issue 219010
Fixed RD "Report on Descendant" access to application page
Resolved in Pega Version 7.2
A report definition using the "Report on Descendant" option worked when executed from a user session but did not work when executed by a File Listener Process. This was due to the report not being able to access the application page in the batch requestor context, and has been corrected.
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.