INC-159759 · Issue 629624
Report title displayed for empty widget charts
Resolved in Pega Version 8.6
Per design if there is no data to be rendered in the chart from a report added in a Widget in any portal, a static image is displayed saying "No Data to Display". However, if there were multiple reports in the Widget it caused confusion on which report was not being displayed because the image did not show the title of the report. To resolve this, an enhancement has been added to modify pzRRChartDiv to display the report Title even when there is no data in it.
INC-160178 · Issue 632897
Local time used for report filters
Resolved in Pega Version 8.6
The date format in the filter condition of the report was being displayed in GMT format rather than the Local time Format. This has been corrected.
INC-160825 · Issue 629369
Search landing page performance improved
Resolved in Pega Version 8.6
Performance improvements have been made for the Pega Platform search landing page by implementing timeouts for all requests to ElasticSearch when executing PegaIndexAdminImpl.getIndicesInfo() and changing all requests for single index to requests for all indexes. In addition, SearchUtils.areDummyDocumentsPresent() has been modified to get all 'dummy documents' in case there are duplicate dummy documents in the ElasticSearch indexes.
INC-SR-D91660 · Issue 555725
Updated document ID handling for deleting indexes
Resolved in Pega Version 8.6
When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.
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.