INC-174686 · Issue 670542
Handling updated for INativeSQLBuilder with ABAC enabled
Resolved in Pega Version 8.7
When trying to import into a data type, the error "Exception occurred during data import pxW-886: java.lang.IllegalArgumentException: INativeSQLBuilder not initialized properly" was generated. Investigation showed that when Add or Update was chosen with ABAC enabled during import, a null pointer exception occurred while getting the class definition. This has been handled by adding an extra null condition check.
INC-175622 · Issue 652280
Screen reader announces report names
Resolved in Pega Version 8.7
An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.
INC-175797 · Issue 662048
Date/time filter works in source column
Resolved in Pega Version 8.7
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".
INC-176158 · Issue 664348
Max number of rows setting properly honored
Resolved in Pega Version 8.7
The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.
INC-176173 · Issue 654726
Re-indexing correctly triggers old index deletion
Resolved in Pega Version 8.7
There was no request to delete the old index when a new reindexing process was started, resulting in the new data being put into the already existing index. This was traced to a logic flaw which evaluated a condition as false under certain conditions. This 'If' condition has been fixed and simplified so the process responsible for recreating the ElasticSearch index is accessible for the scenario of reindexing an entire index without specifying include or exclude classes.
INC-176205 · Issue 655938
Secure shared link generation added to scheduled reports
Resolved in Pega Version 8.7
When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function.
INC-176385 · Issue 657670
Corrected blank lines for hidden report filter criteria
Resolved in Pega Version 8.7
When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid.
INC-178663 · Issue 659805
Updated handling for batch indexing cancellation
Resolved in Pega Version 8.7
Entries were seen in the pyBatchindex QP even when indexing was not in progress. Investigation showed that if an exception occurred during the cancel process, the pyStatusWork property in Log-Cluster-FTSIndex instance was not correctly updated and the value remained as CancelInProgress. As a result, SLP silently remained in the state of waiting for the completion of cancel operation. This has been resolved by updating the handling of the cancellation process to ensure the queue is correctly cleared and email notifications are sent as expected.
INC-178999 · Issue 658730
Batch indexing double submission corrected
Resolved in Pega Version 8.7
It was possible to double-click and initiate two batch indexing requests against the same dedicated index, one immediately after the other, creating a double-sized index. This was a missed use case for refreshing the page to disable the re-index button after the first click, and has been corrected.
INC-181394 · Issue 662098
Handling added to avoid incorrect manifest count
Resolved in Pega Version 8.7
Extracted Record counts in the manifest file were incorrect if any updates were made during the extraction process. This has been resolved by modifying the code to prevent the issue.