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.
SR-B42679 · Issue 307394
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-B57039 · Issue 312472
Removed space in data transform value
Resolved in Pega Version 7.3.1
After running a Summary View with Trend Reporting, the following error was logged: NumberFormatException For input string;" ". When trend reporting is enabled in list view with no value for pyCeilingField, the data transform initialized this value to " " instead of "", causing the issue. This has been fixed.
SR-B53579 · Issue 315392
Filtering works for multiple columns inside a report
Resolved in Pega Version 7.3.1
After upgrade, the filtering option inside a report worked when filtering a single column but did not work for filtering more than one column. This was caused by an error in RDCommonUtils.removeTokenFromExpression() that did not correctly consider the logic if it contained "and"; it has been fixed.
SR-B55564 · Issue 311340
Chart image export to PDF added
Resolved in Pega Version 7.3.1
An enhancement has been added to allow Export to PDF for standalone charts using the "Save as image" option.
SR-B53490 · Issue 311967
Filters repaired for report definition columns
Resolved in Pega Version 7.3.1
Filter on the report definition column was not working as expected and returning all of the results instead of only the filtered items. This was traced to whitespace in the filter logic name, and has been corrected