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-B66844 · Issue 317078
RD modified to allow more than 1000 entries in a filter value
Resolved in Pega Version 7.3.1
A DB exception was thrown when a report definition was run with more than 1000 entries in a filter value. This was due to the DB limitation, and the system has been updated to pass the "pyReportParamPageName" parameter to RD to avoid the exception.
SR-B50800 · Issue 311591
Fixed sorting of nested repeat grid with one child-grid column
Resolved in Pega Version 7.3.1
A Null Pointer Exception was generated when performing a sort in a nested Repeat grid when the child-grid had one column and sort was enabled. The sort worked as expected when there was more than one row in the embedded/child grid. This was due to a loss of the content div after the first sort, and has been corrected.
SR-B41245 · Issue 315783
Query Generation layer Null Pointer Exception handling added to support Sybase and other DBs
Resolved in Pega Version 7.3.1
A Null Pointer Exception was generated while running a report that connected to a table on a Sybase database which had a nvarchar column. In order to handle Sybase requests or other unexpected DBs used with Pega, the DB_Type.GENERIC in mapDatabaseType in DatabaseUtils.java class has been updated to handle any Null Pointer Exceptions that might be encountered in the Query Generation layer.