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.
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-101011 · Issue 556725
Pulse mentions correctly tagged in Google Chrome
Resolved in Pega Version 8.4.2
Pulse mentions of spaces or users were not getting tagged correctly. This issue was due to recent changes in the way touch events are handled in Google Chrome: the latest upgrade removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. As part of the work done to resolve this, it was discovered that the initAutocomplete function in the pzJquerymentionsInput .js was failing to delegate the mousedown event. This has been corrected by delegating touchstart and mousedown while initializing if screen isTouchable.
INC-119803 · Issue 561686
Placeholder text added for question dropdown sourced by a datapage
Resolved in Pega Version 8.4.2
In a flow action with question pages where each question page was configured with a set of question rules, one question which displayed a country list in a dropdown sourced from a datapage always displayed the first value by default in the dropdown instead of place holder text (like Select..). In addition, the default selection value of the dropdown was not saving to the clipboard on submission of the flow action, causing it to appear in the UI like the first value had been selected even though nothing was saved on the clipboard. These issues have been resolved by adding place holder text in pzSetQuestionStreamSimpleDynamicSelect for a dropdown with a datapage source
INC-120326 · Issue 564438
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.4.2
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
INC-126114 · Issue 562178
Spaces member count method updated
Resolved in Pega Version 8.4.2
When a space contained more than 50 members, it always displayed the count as 50 even though the Spaces section showed the correct count. This was due to a pagination setting that had a maximum of 50 records set, and has been resolved by using the GroupMemberCount DP instead of AllMembers to retrieve an accurate count.