INC-174686 · Issue 670540
Handling updated for INativeSQLBuilder with ABAC enabled
Resolved in Pega Version 8.6.2
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-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-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-168003 · Issue 655375
BIX Total Instance count matches manifest
Resolved in Pega Version 8.7
The BIX Manifest file was showing a count mismatch when the BIX Manifest and Extract files were shared with downstream teams, causing data to not be accepted by the downstream application. Investigation showed this occurred for an embedded page list property in the sequence that was missed and not considered. To resolve this, a DSS has been added: when BIX/generateAllEmptySubscriptForPageList is set to true, an empty subscript will be generated for the missed properties.
SR-B56777 · Issue 312300
Vertical scrollbar refinements for report editor
Resolved in Pega Version 7.3.1
To fix a previous scrolling problem, the layout of the report editor was altered to accommodate a vertically resizing header. This involved removing the absolute positioning of the sidebar and main panel that allowed independent scrolling. This has been further refined to use flexbox to prevent wrapping in the header (on desktop only).
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-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.
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.
INC-185565 · Issue 667508
Helper text added to improve close icon accessibility
Resolved in Pega Version 8.6.2
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-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.