INC-119669 · Issue 562588
Special character handling added to filters for table sourced with parameterized RD
Resolved in Pega Version 8.1.9
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
INC-145810 · Issue 599463
BIX log shows correct corrupted BLOB pzInskey
Resolved in Pega Version 8.1.9
An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.
SR-D90400 · Issue 563187
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.1.9
When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.
INC-151293 · Issue 630346
Out of memory condition resolved for BIX extraction
Resolved in Pega Version 8.5.4
A node was going down automatically during execution of a BIX Extract rule when working with old objects. Investigation showed this was related to an out of memory error: the work object had nested page lists, and when one of the page lists contained a propertylist which contained more records, the system was trying to add entries to the LinkedList if any properties were missing the reference during extraction. Because LinkedList allowed duplicates, it filled with enough errors to cause the out of memory condition. To resolve this, LinkedList has been replaced with LinkedHasSet, which does not allow duplicates.
INC-158473 · Issue 626278
BLOB decryption API updated for greater flexibility
Resolved in Pega Version 8.5.4
A BIX extraction issue occurred after the class had enabled BLOB Encryption. The errors indicated the BLOB had been persisted in an incorrect stage, causing the extraction of the single item to never complete even though some CSV file was created. This was traced to the API used to read the encrypted BLOB, DatabaseUtilsCommonImpl.getStreamBytes, which had the limitation of decrypting only when a Site-specific cipher existed. To resolve this, the system has been modified to use a different API which works for all encryption modes, PageDatabaseMapperImpl.getStreamBytes().
INC-159759 · Issue 629625
Report title displayed for empty widget charts
Resolved in Pega Version 8.5.4
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 632896
Local time used for report filters
Resolved in Pega Version 8.5.4
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-160608 · Issue 648635
Added handling for missing deleted/report shortcut for drilldown
Resolved in Pega Version 8.5.4
Whenever “Report Details” for a drilldown report without category was clicked, a Flow Action Error was generated. This was due to a missing Report shortcut normally stored in the Report Definition, and has been resolved by modifying pzPreProcessReportDetails to handle the edge case of a shortcut not present/deleted for a drill-down report.
INC-162649 · Issue 639399
DSS added for handling missing attachments
Resolved in Pega Version 8.5.4
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.
INC-163173 · Issue 651077
Datatype import updated to handle null value
Resolved in Pega Version 8.5.4
After upgrade, attempting to import CSV files in Data type using the import option provided was not working. This was traced to the AccessPolicy Filter value being set to null in the filterLogic, and has been resolved by modifying the 'if' condition in the NativeSQLSecurityPolicyHelper file to handle an empty value in the logic string of an access control policy condition for a datatype class.