SR-A5814 · Issue 216307
Resolved blank list page navigation
Resolved in Pega Version 7.2
If there was a backslash (escape characters) in the double quoted report parameters passed from the section, no data was shown when navigating to the next page in a ListView report. This was caused by multiple encodings of the escape characters while moving back and forth between the pages. The filtering has been updated to correct this issue.
SR-A6387 · Issue 216159
Resolved errors while saving in summary view
Resolved in Pega Version 7.2
While saving an existing summary view, the error message "Output type: ** Your Field Definition does not match with Chart Definition. Verify it" was generated if only the third column was selected at the time of the save. In addition, selecting any checkbox other than the first in the chart's data tab during save of the summary throws an error. These issues have been fixed.
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-A12707 · Issue 229383
Subreport join/filter updated
Resolved in Pega Version 7.2
An invalid subreport join/filter condition error was thrown if a filter with an unoptimized property from a sub report on one side had an optimized or literal property on the other side, even if the prconfig setting "reporting/useStreamInJoinConditions" was set to true. This has been fixed.
SR-A9129 · Issue 220717
Report Definition error message localized
Resolved in Pega Version 7.2
Localization/customization has been added for the Report Definition error message : "Retrieving the report data exceeded the limit of * seconds. Please try making the report more specific by further limiting which rows to include".
SR-A12941 · Issue 224444
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
SR-A12941 · Issue 230561
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
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.