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.
SR-A7716 · Issue 219147
Proper value separations in filtered report definitions
Resolved in Pega Version 7.2
In a report definition in edit mode, trying to set filtering on several value was causing values to be appended without proper separators. As a result, no results were found when trying to apply a filter. This was due to a conflict in visibility conditions for the DataType identifier , and has been fixed.
INC-189136 · Issue 679516
Dataflow with report definition source repaired
Resolved in Pega Version 8.7
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-197610 · Issue 688003
Dataflow with report definition source repaired
Resolved in Pega Version 8.7
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
SR-A5814 · Issue 216307
Resolved blank list page navigation
Resolved in Pega Version 7.2
If there was a backslash (escape characters) in the double quoted report parameters passed from the section, no data was shown when navigating to the next page in a ListView report. This was caused by multiple encodings of the escape characters while moving back and forth between the pages. The filtering has been updated to correct this issue.
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.
SR-A1999 · Issue 214345
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.
SR-A1999 · Issue 214460
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.
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-162649 · Issue 639400
DSS added for handling missing attachments
Resolved in Pega Version 8.7
When an S3 repository was configured as storage, some cases were not coming up in search and exception errors were seen in logs for a deleted attachment after every system restart/re-indexing of the search. Investigation showed these case objects were in the broken queue for pyFTSIncrementalIndexer due to a null pointer error encountered when indexing the attachment, and that the attachments were available in the repository but could not be read from the attachment repository during indexing. To resolve this, a new DSS setting has been added which allows selecting one of two behaviors: * Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = true : broken item is generated, but with a meaningful error message. This is the default behavior * Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = false: case is indexed, but without the problematic attachment. Error message is printed out to the logs.