SR-B6161 · Issue 275612
RD generating checkbox control as T/F image fixed
Resolved in Pega Version 7.3
A report definition was not showing checkbox controls as images for true/false properties when generated automatically. This has been fixed.
SR-B6292 · Issue 276738
New accessibility control for adding explicit text to RB column headers
Resolved in Pega Version 7.3
In order to create report browser column headers with explicit text for accessible users, a new available control named pyReportBrowserControl that uses the parameter "Type" has been added to the pzRBShortcutsGrid7 section.
SR-B796 · Issue 283050
Report Definition updated to handle null value field grouping
Resolved in Pega Version 7.3
Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.
SR-B796 · Issue 277684
Report Definition updated to handle null value field grouping
Resolved in Pega Version 7.3
Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.
SR-B9137 · Issue 278539
RD column context menu alignment fixed
Resolved in Pega Version 7.3
On a report definition with many columns, scrolling to the right caused the column context menu to not be aligned with the column. The menu alignment code calculations have been modified to correct this.
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.
SR-B42679 · Issue 303776
Report definition popup display overwrites single window
Resolved in Pega Version 7.3.1
Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.
SR-B42679 · Issue 305263
Report definition popup display overwrites single window
Resolved in Pega Version 7.3.1
Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.