SR-D54120 · Issue 541352
Improved handling for attachments not using UTF-8 encoding
Resolved in Pega Version 8.5
When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.
SR-D68235 · Issue 534782
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.5
The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.
SR-D89428 · Issue 550392
Data Flow StartTime uses locale timezone
Resolved in Pega Version 8.5
The start time of the dataflow was displayed in GMT instead of the operator locale timezone. This has been corrected.
SR-D77157 · Issue 544472
DataSet preview will use date instead of datetime
Resolved in Pega Version 8.5
While using a DataSet preview functionality, the date appeared as reduced by one day. This has been resolved by parsing date as 'date' instead of 'datetime' to avoid issues with timezone interactions.
SR-D68328 · Issue 557750
Unload handler added for use with custom popups
Resolved in Pega Version 8.5
A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.
SR-D84480 · Issue 546188
FilterHistory decision tree used for audit log status
Resolved in Pega Version 8.5
Attempting to use the “FilterHistory” decision tree in the work class to return value “false” for “pyCloseOpenAssignmentsOnResolution” to hide the “pyCloseOpenAssignmentsOnResolution” field value (“Unfinished assignments were cleaned up by the system after the completion.. ”) from history was not working as expected, and still returned the audit message. This was due to the system setting this AuditNote parameter within the “pzProcessResolutionStage” activity, where Param.UpdateHistory was set to true always. In order to support more flexibility, the Param.updateHistory paramter in step3 of the pzProcessResolutionStage activity will be set based on the FilterHistory decision tree. When set to false in FilterHistory decision tree, pyCloseOpenAssignmentsOnResolution will be set as false and audit will not be logged.
SR-D86360 · Issue 548571
Handling added for declare expression targets when harnessid is null
Resolved in Pega Version 8.5
Client expression calculation was not happening in Perform harness. Research showed that whenever text input calculations happened, the expression_calculation js setTargetValuesSuccess function was called but the elementList parameter was passed as null due to the inputHarnessId parameter being undefined. This has been resolved.
SR-D90331 · Issue 553608
Context-specific APIs used for RefreshHarness with AJAX container
Resolved in Pega Version 8.5
After creating an interaction case and letting it go idle, attempting to continue and process the service cases in that case was intermittently resulting in a transaction ID mismatch error. This was traced to handling in the AJAX container, and has been resolved by updating the system to use context-specific APIs for refreshHarness case in doc_submit.
SR-D81726 · Issue 544010
Corrected refresh section for grid dropdown using Google Chrome
Resolved in Pega Version 8.5
When using the Google Chrome browser on a Windows machine, an incorrect click event fired when dropdown options were changed inside a grid was causing refresh section to not work properly. This has been resolved by suppressing the 'click' action on dropdown in the 'ui_events.js' file.
SR-D85400 · Issue 549061
Reset focus to Rich-text editor after Spellchecker use
Resolved in Pega Version 8.5
After correcting the misspelled words as suggested by SpellChecker, the corrected words were not reflected in the email. This was traced to a focus issue in Rich-text editor, and has been resolved by ensuring the focus is returned to Rich-text editor once the suggested corrections are accepted.