SR-A22750 · Issue 244061
Case Stages status updated by automated process
Resolved in Pega Version 7.2.1
Case stages that were completed by an automated process and not a person maintained their default "Future" status in the Case Stages data page instead of being marked "Past". The stage completion status is determined by value in "pxCompletedBy", but this field was empty due to the automation. A check has been added to resolve this.
SR-A22794 · Issue 245278
parseXML able to map multiple values
Resolved in Pega Version 7.2.1
In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.
SR-A22813 · Issue 244103
Apostrophe(') escaped in tooltip property
Resolved in Pega Version 7.2.1
Whenever there was an apostrophe in the radio button's tooltip property, all the content of the tooltip after the apostrophe was not considered. When inspected in DOM, the label's title was considered only until apostrophe with all the remaining being generated out of title attribute and hidden. This has been fixed by properly escaping the apostrophe.
SR-A22816 · Issue 246151
Message clearing CME error fixed
Resolved in Pega Version 7.2.1
A Concurrent Modification Exception error as thrown in logs when navigating to from one row to another row in tree grid due to a data page being loaded while trying to clear messages in a page. This has been resolved by disabling auto populate while in the process of clearing messages in a page.
SR-A22841 · Issue 245073
All Data Flow keys considered for filtering
Resolved in Pega Version 7.2.1
When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.
SR-A22933 · Issue 241566
Check added to resolve Google Chrome-based value localization error
Resolved in Pega Version 7.2.1
A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.
SR-A22933 · Issue 246958
Check added to resolve Google Chrome-based value localization error
Resolved in Pega Version 7.2.1
A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.
SR-A22958 · Issue 247141
Mobile Client passivation fixed
Resolved in Pega Version 7.2.1
Data pages were not being properly passivated in the mobile client. This was traced to an exception generated by the isFromDictionaryFlag() function when navigating to or from PRE assignment to any other assignment in the flow after hitting unknown list and unknown group settings. As the isFromDictionary function is not necessary here, it has been removed.
SR-A22982 · Issue 249598
Resolved memory leak in ActionRequestRegistrarContainer cleanup
Resolved in Pega Version 7.2.1
A memory leak was traced to ActionRequestRegistrarContainer objects not being garbage collected. In the Tampering protection feature, an ActionRequest Registrar per HarnessID is still created in ALLOW mode, however it will not be removed as done in the cases of WARN and DENY modes. To resolve this, the system has been updated to not create containers in ''ALLOW" mode.
SR-A22993 · Issue 247098
Date format and alignment updated for Export to Excel
Resolved in Pega Version 7.2.1
When using Report Definition for a case search with the out-of-the-box excel export, formatting one of the DateTime type properties to display only the date portion in the exported report was not working as expected in the repeated-grid while it did work properly in report definition export function. The problem existed in the generation for the Report Definition itself due to the control formatting the data to be mm/dd/yyyy without the days even though the data type is a datetime, and the function has been updated to pass "date" as the datatype when a datetime is being formatted as a date.