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-D18879 · Issue 500640
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.3.1
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D21527 · Issue 491736
Hidden filters will not be shown on the resulting report
Resolved in Pega Version 8.3.1
After setting up a Report Definition to be visible in report browser with all filters hidden, editing and saving the report resulted in the filter values being visible on the report. This has been resolved by modifying pzResolveCopyFilters activity so that If the filter view option is "Read only, allow no changes" and "Filter not visible in Viewer", it will skip copying the filter values on to the report definition page.
SR-D22885 · Issue 494162
Added check for empty class properties to report scheduler
Resolved in Pega Version 8.3.1
A report that was looking for events in the most recent X hours by using the "Difference In Hours" filter function ran in the foreground but failed with an exception when running under the scheduler. The same report ran as expected in background without the filter. This was traced to a classname property not being set on the clipboard, and has been resolved by adding a check for empty classes on the clipboard when scheduling a report.
SR-D26815 · Issue 500189
Updated support for numeric values in text columns during Excel export
Resolved in Pega Version 8.3.1
After creating a report definition that included currency and percentage as a columns, the currency, percentage, and number format were not shown as expected for the locale when the report was exported to Excel. This was an inadvertent side effect of work performed to resolve issues for text columns formatted by non-numeric controls, and has been resolved by moving the support for numeric values in Text columns from ReportUIField to NumericReportUIField.
SR-D27528 · Issue 501369
Return from drilldown in frameless portal corrected
Resolved in Pega Version 8.3.1
Drill up after drilling down on a dashboard chart in a frameless portal (such as Case Worker or Case Default) was throwing an exception. This was caused by the top-level page generated during drilldown not having pyRetainPage set to true, causing it to be removed from the clipboard by doUIAction. This has been resolved by updating runReport to set pyRetainPage if it needs to create the top-level page.
SR-D27687 · Issue 500051
Mashup Export to Excel works on first use
Resolved in Pega Version 8.3.1
If a report was opened from Mashup and exported to Excel, only one record was given regardless of the actual size of the report. If the mashup main page was refreshed, the open and export process worked correctly. This has been corrected by adding a call to pzSetQueryDefaults in pzRDExportWrapper when the requestor is initialized for Mashup.