INC-181684 · Issue 665484
Privileges adjusted for RetrieveReportData
Resolved in Pega Version 8.7
In recent versions of Pega, pxRetrieveReportData was secured with @baseclass AllFlows and OpenDeveloperForm privileges. However, this can interfere with setting up roles after update. To resolve this, the privilege restrictions have been removed from pxRetrieveReportData as it is already protected by ABAC/RBAC.
INC-182193 · Issue 674801
Drilldown report takes original report prompt parameters
Resolved in Pega Version 8.7
When a report had prompt filters configured and the summary report definition was executed by giving prompt filters, drilling down to one of the records in the summary report display and then looking at the reports displayed and summarized on a column showed a mismatched count. This was found to be a very specific edge case that involved calling the "Summarize" action from a report column within a drilldown report when using a custom filter section and "prompt for filter changes" on the main report. Filters from the custom filter section were being propagated to the drilldown report when summarizing, but the drilled-down-and-summarized report itself had not been refreshed on the client side to reflect this. To resolve this, the actions have been copied from pyDefaultCustomFilterApplyCancel and applied to the Summarize selection in pzGridMenuNavRule.
INC-182375 · Issue 664344
Report filter description correctly displayed
Resolved in Pega Version 8.7
When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.
INC-182534 · Issue 677142
Resolved Sub Report Filter Criteria error
Resolved in Pega Version 8.7
After upgrade from Pega 7 to Pega 8, Sub Report filter criteria were throwing a runtime error when pyPartyFullName from Index-WorkPartyUri was used as a filter condition. Under certain conditions, Sub Report and Main report use class joins with the Index-WorkPartyUri table to get the count of cases. In this case, the error was caused by the ValidateFilterValue edit rule passing the wrong class name for the sub report class join property. This has been resolved.
INC-183553 · Issue 666396
Report Scheduler Email Notification column consistently populated
Resolved in Pega Version 8.7
The Email Notification column in the Report Scheduler was not being populated. Analysis showed that some standard rules were being skipped for some list view reports; this has been resolved by including the pzReportBrowserScripts js file under the scripts of the pyReportBrowser harness so that it will reload the pzReportBrowserInner while unloading the model popup.
INC-183960 · Issue 674381
Cases Created through email bots remains searchable
Resolved in Pega Version 8.7
When a case was created through Email Bot, the delete attachment link in pzCreateTriageWork activity was triggering a delete event in incremental indexing that removed the main work object. This has been resolved by adding a condition check in the SearchIncrementalIndexNotifier class for the link page, and the work object will be updated instead of deleted.
INC-184303 · Issue 670404
Runshortcut updated to allow direct invocation for reporting
Resolved in Pega Version 8.7
After update, reports were not running as expected. This was traced to the checkbox for 'Allow direct invocation from the client or a service' not being checked in the final rule, preventing reports from working if they were called using the activity pxRunshortcut. This has been resolved by resetting the checkbox to checked.
INC-185565 · Issue 667509
Helper text added to improve close icon accessibility
Resolved in Pega Version 8.7
After opening a report, the "X" close icon was not read by JAWS and was not functional when JAWS was running. Investigation showed that the ReportEditorHeader section did not have Helper Text for the Close icon; this has been added to improve accessibility.
INC-185727 · Issue 668211
Updated replica management for search clusters
Resolved in Pega Version 8.7
When using a cluster with two Universal nodes in the cluster, a daily restart process where the second node was not started until the first was fully up resulted in Search initialization failing for the first node while becoming active on the second node. This was traced to the methods used in increasing and decreasing replicas. This has been resolved by revising the handling of ElasticSearch node lifecycle and replicas through a new option "Dindex.searchNodeCount " which includes a specification for the number of expected search nodes. If this option is not present, the old method will be used.
INC-186138 · Issue 668811
Charts sourced from Report Definition show correct color post-update
Resolved in Pega Version 8.7
After update, the color coding was not working on charts sourced from a report definition. This was due to the correct seriesType not being determined when function aliases were used in charts, and has been resolved by adding a condition in configuration.java to determine correct the SeriesType.