INC-131942 · Issue 574322
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.2.8
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.
INC-135719 · Issue 580689
Corrected reference exception for filter on a grid sourced from a parameterized report definition
Resolved in Pega Version 8.2.8
An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.
INC-140110 · Issue 600399
Large filter values accepted in Report Definition edit
Resolved in Pega Version 8.2.8
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 596470
Scheduled tasks landing page shows all tasks
Resolved in Pega Version 8.2.8
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.
INC-144756 · Issue 602724
Security improved for searches
Resolved in Pega Version 8.2.8
Authentication requirements have been added to activities associated with searching.
INC-120343 · Issue 573075
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.2.8
When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.
SR-D90400 · Issue 563185
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.2.8
When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.
SR-117877 · Issue 178627
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.
SR-117877 · Issue 175972
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.
SR-118224 · Issue 182305
Report Definition "Pick Value" list resolves to correct layer
Resolved in Pega Version 7.1.8
When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.