SR-A17016 · Issue 234926
Repaired multiple-value filters for RD data transform
Resolved in Pega Version 7.2.1
When using a report definition in which the filter values were supplied through the data transform rule, a single given value was correctly passed but multiple values were not. This was traced to the encoding of double quotes which were then not replaced in the correct step, and has been fixed.
SR-A17065 · Issue 233138
Support added for custom XSS headers
Resolved in Pega Version 7.2.1
After upgrade, problems were found with setting XSS headers. To resolve this, the new Dynamic System Setting "http/responseHeaders" has been added to support custom HttpResponseHeaders.
SR-A17338 · Issue 233583
Upgrade error resolved for localized rulesets in custom access group
Resolved in Pega Version 7.2.1
Due to an error in the MostFrequentlyUsedMap code, upgrading was failing if a particular environment had Requestor Type records referencing a custom Access Group that had localized rulesets. This has been fixed.
SR-A17425 · Issue 233173
Memory leak fixed in Field Value Conclusion Cache
Resolved in Pega Version 7.2.1
A memory leak was found with Field Value Conclusion caching not being correctly cleared of the dummy conclusion values for null objects. This as been resolved.
SR-A17488 · Issue 234010
Corrected truncation of localized text in Report Viewer filters
Resolved in Pega Version 7.2.1
The localized test "Select Values" text was being truncated in the Report Viewer filters were enabled. This setting has been updated to take the additional width without truncating.
SR-A17497 · Issue 234925
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.
SR-A17758 · Issue 234057
Check added to avoid duplicate encryption
Resolved in Pega Version 7.2.1
When a property of type TextEncrypted was edited from the clipboard viewer, the encrypted value was being encrypted again. This was caused by the server side trimming the string values of parameters sent in a post body, removing '\t' from the encrypted value '\t{ps}XXXXX' and triggering encryption of an already encrypted value. To prevent this, the system has a check for strings starting with '\t{ps}' at the time of parsing URL Parameters or post body.
SR-A17773 · Issue 234118
Custom field value visible for maxloginattempts message
Resolved in Pega Version 7.2.1
In order to support a customized field value message once a user crosses the allowed invalid login attempts threshold, a new overloaded method of prepareStatusInfo() has been introduced in PRDiagnosticStream.java that will not mask the exception details with generic error message.
SR-A17916 · Issue 234503
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.
SR-A17916 · Issue 233771
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.