SR-A12638 · Issue 223936
Check added to handle mismatched property names given in referred page
Resolved in Pega Version 7.2
If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.
SR-A7008 · Issue 216642
Number separators localized for Excel export handling
Resolved in Pega Version 7.2
While using the Export to Excel button in reports, some of the figures in numbers columns displayed warning messages indicating they were formatted as text. This was a localization issue where numbers containing unusual separators were interpreted as strings, and has been resolved with a code change that allows Excel to decide the right format based on locale.
SR-A5758 · Issue 218426
Corrected automatic decimal rounding in summary report
Resolved in Pega Version 7.2
In the summary view report grand total, decimal values having 4 digits after the decimal point were being rounded to two places and displaying two zeroes in the 3rd and 4th decimal places. Ex: 1.1234 + 2.2345 returned 3.3500 instead of 3.3579. This was traced to the format "#.##" being applied to every value in the summary, and has been corrected.
SR-A7716 · Issue 219147
Proper value separations in filtered report definitions
Resolved in Pega Version 7.2
In a report definition in edit mode, trying to set filtering on several value was causing values to be appended without proper separators. As a result, no results were found when trying to apply a filter. This was due to a conflict in visibility conditions for the DataType identifier , and has been fixed.
SR-A10501 · Issue 223738
Corrected date format for chart using custom DateTime filter
Resolved in Pega Version 7.2
The date format of legends for a chart was not being formatted properly if a Filter Criteria range was used on the Datetime property. This has been corrected.
SR-A10369 · Issue 221614
Listview list query accepts non-date criteria
Resolved in Pega Version 7.2
The Listview list query was not being refreshed if the criteria values were taken from Time Period. This was due to the pyConditionValue1purpose not populating properly when given a non-Date data type setting, and had been corrected.
SR-A10282 · Issue 222249
RD summarize menu context fixed
Resolved in Pega Version 7.2
When attempting to use Summarize functionality using a report definition, the Menu context page was not calculated properly due to an issue with the AggregateWrapper resolution of the input. This has been fixed.
SR-A12102 · Issue 223002
Report schedule button visibility fixed in Case Manager Portal
Resolved in Pega Version 7.2
It was not possible to schedule standard reports from the Case Manager Portal if the check out option was disabled. This was an error in the display of the scheduling button, as an operator who is capable of running a report should also have the capability to schedule it, and has been corrected.
SR-A11563 · Issue 224698
XSS security added to data table edits
Resolved in Pega Version 7.2
When editing a data table and saving the record, the request could be intercepted and a vulnerable string added to the pageIndex parameter. XSS security has been added to this function.
SR-A11563 · Issue 224698
XSS security update for TabbedRepeatingListSection
Resolved in Pega Version 7.2
Security updates have been made to the TabbedRepeatingListSection function to close a potential XSS vulnerability.