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.
SR-A23012 · Issue 242327
pega.u.d.onViewUpdatecorrectly triggered from Master-Detail
Resolved in Pega Version 7.2.1
The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.
SR-A23012 · Issue 243963
pega.u.d.onViewUpdatecorrectly triggered from Master-Detail
Resolved in Pega Version 7.2.1
The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.
SR-A23035 · Issue 245109
Enabled bulk delete of ADM models
Resolved in Pega Version 7.2.1
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.