SR-B960 · Issue 271764
PDF "Display Report Filter" check honored
Resolved in Pega Version 7.2.2
The filter layout was visible in a generated PDF despite "Display Report Filter" being unchecked. This was the fault of a missed visibility condition in pzDisplayReportSectionForPDF, which has now been added.
SR-A89677 · Issue 257766
Removed erroneous warning from auto-created DataType reports
Resolved in Pega Version 7.2.2
When creating a data type and local source, a report definition is automatically generated for the data type. That report definition contains the warning "Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls." This was confusing, creating the unintended assumption that something was wrong with the automatically generated report. To clarify this, the warning will not be displayed when the rule is created automatically.
SR-A96539 · Issue 264614
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
SR-A96539 · Issue 265411
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
SR-A91955 · Issue 260732
Filter icon made accessible
Resolved in Pega Version 7.2.2
When the Enable accessibility add-on was checked, the filter icon was not selectable. This has been corrected.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
SR-A77395 · Issue 255085
DB2 external mapping values used for filtering
Resolved in Pega Version 7.2.2
When using the "External Mapping" feature in a class to map column names to different property names in DB2, the filter conditions in a report definition rule either generated incorrect SQL in the report viewer for "Select Values" or the error "There was a problem getting a list" appeared. This error was caused by the SQL query using the property name instead of the column name, leading to external mapping for the properties not being considered. The pzGetAvailableValues activity has been modified to get the correct column name based on external mapping.
SR-D19299 · Issue 511323
Support added for calling Export to Excel directly from Report Definition
Resolved in Pega Version 8.2.5
When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.
SR-D34655 · Issue 513421
Deferred load works inside custom row section of Report Definition
Resolved in Pega Version 8.2.5
Deferred Load was not working inside a custom row section of a report definition. This was traced to the non-auto-generated mark up written for the customRowSection include not having the node_type="MAIN_RULE" name="BASE_REF" id="RULE_KEY" base_ref="" attributes. This led to the load manager which performs the defer load to get the base_ref as "pyReportContent" from the "ReportDisplay" section dom node. To resolve this, the RRDataListGeneration has been modified to set the proper base_ref to customRowSection include so the context/base_ref is passed to the customRowSection.
SR-D36265 · Issue 509607
Export to Excel total result count disabled
Resolved in Pega Version 8.2.5
After upgrade, an imported report with more than 30k records took an excessive amount of time (6-7 minutes) to be exported to Excel after being run, and the resulting Excel file only contained one record. A child report having around same number of records was exported successfully in around 30 seconds. Analysis showed that during the export process, a thread dump was originating from the thread responsible for performing export. Co-relating this with alert logs showed a PEGA0042 alert around the packaging of the query. This was traced to the paging settings on the pyContentPage not getting properly set from the activity pxRetrieveReportData on step 14: the boolean that sets .pyContent.pyPaging.pyReturnTotalResultCount used a page that will always be empty on the upgraded system, leading to an error in calculating the total result count. To resolve this, fetching the total result count on Export to Excel has been disabled.