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.
INC-168203 · Issue 641338
Improved performance for data flow runs
Resolved in Pega Version 8.5.4
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-169856 · Issue 649459
Personalized table sort order limited
Resolved in Pega Version 8.5.4
After implementing a personalized table, the query started adding more 'order by' sorts, causing system impact. This was traced to the pzPopulateSortOrder activity Implementation having different constants assumed for the same purpose (999 in one place and 99999 in another), and has been resolved by updating the logic in step 1 and step 2 to disregard sort orders higher than 999.
INC-170389 · Issue 645002
Updated authentication for report filter screen
Resolved in Pega Version 8.5.4
If the report filter screen was shown first after clicking on the report link in the report browser, an error is generated for users but not for administrators. This has been resolved by registering the activity and adding a BAC registration section to the prompt filter section.
INC-185824 · Issue 676628
Corrected filtered column list sorting in Report Browser
Resolved in Pega Version 8.8
Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.
INC-198725 · Issue 707483
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.8
Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.
INC-201219 · Issue 696610
Updated chart button markup
Resolved in Pega Version 8.8
Some of the buttons were incorrectly displayed while clicking "Edit Report" from the Cosmos report browser. This was due to the buttons generating markup that was used to support older browsers in pzChartButtons, and has been resolved by updating the button markup.
INC-202447 · Issue 698658
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.8
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.
INC-202480 · Issue 699081
Resolved report filter section freeze
Resolved in Pega Version 8.8
When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.