SR-D55801 · Issue 524293
Corrected HTML error generated on export to PDF
Resolved in Pega Version 8.4
After exporting a report to PDF, the PDF could be viewed but repeated instances of the error "<th> missing ‘>’ for end of tag" were logged. This was traced to missing the closing '>' for th in the pzRRDataListHeaderRow HTML rule when "Enable column command menu" is unchecked in ReportViewer options, and has been corrected.
SR-D58552 · Issue 522088
Report Definition filter editing shows all values correctly
Resolved in Pega Version 8.4
After launching a report, certain values were not populated on the pop-up when editing the filters or the commas separating the values did not appear. This was traced to the activity pzGetSelectedValues containing an older implementation of column type checking, causing it to report some embedded property references as being of type "Included Page" instead of the type of the ultimate property. This has been resolved by updating step 1 to only use this logic if pyDataType is not set, which should already be set for all filters and columns, and the formatting has been corrected.
SR-D65937 · Issue 528980
Support added for calling Export to Excel directly from RD
Resolved in Pega Version 8.4
When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.
INC-151293 · Issue 630347
Out of memory condition resolved for BIX extraction
Resolved in Pega Version 8.6.1
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-160190 · Issue 658126
Logic updated to allow page property and declare index with the same name
Resolved in Pega Version 8.6.1
A Property which was in a page list which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid.
INC-160608 · Issue 648636
Added handling for missing deleted/report shortcut for drilldown
Resolved in Pega Version 8.6.1
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 639398
DSS added for handling missing attachments
Resolved in Pega Version 8.6.1
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-166120 · Issue 657057
Parameter added to prevent name localization in Dev Studio Reports
Resolved in Pega Version 8.6.1
Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup.
INC-168203 · Issue 641337
Improved performance for data flow runs
Resolved in Pega Version 8.6.1
Nodes were intermittently going into safe mode after a service registry heartbeat failure. Investigation found that some of the activities were performing an Obj-Browse that invoked report definition logic to call the database classmap. This has been resolved by modifying the implementation for the initialization and caching of list of classes in a table.
INC-169055 · Issue 646674
Performance improvements for database queries and archiving
Resolved in Pega Version 8.6.1
In order to improve the performance of database queries, repetitive unnecessary database calls have been removed, archival queries have been simplified, and diagnostic metrics were added. Optional batch requestors have been added to all archival services with their own DSS settings to allow processing more cases in parallel. It is recommended to create 2 additional indexes to help with the archival process. The indexes will be on:pegadata.pr_metadata (pyisparent, pyobjclass, pyarchivestatus) INCLUDE (pyinskey); pegadata.pr_metadata (pyisparent, pyarchivestatus) INCLUDE (pyinskey);