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.
INC-127102 · Issue 602699
Synchronized BatchStatus email available for multi-node
Resolved in Pega Version 8.4.4
An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.
INC-133482 · Issue 605004
Corrected isExternal flag not resetting
Resolved in Pega Version 8.4.4
If an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.
INC-140110 · Issue 600400
Large filter values accepted in Report Definition edit
Resolved in Pega Version 8.4.4
Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.
INC-143191 · Issue 596467
Scheduled tasks landing page shows all tasks
Resolved in Pega Version 8.4.4
Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.