INC-136264 · Issue 582469
Chatbot text starts scroll at top of answer
Resolved in Pega Version 8.2.8
In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.
INC-127591 · Issue 564818
isAuthenticated checks trimmed for Performance Improvement
Resolved in Pega Version 8.2.7
In order to improve performance, a duplicate check of pxIsRepositoryAuthenticated has been removed from the Function Rule.
INC-127859 · Issue 564619
Email image retrieval switched to Lazy Load
Resolved in Pega Version 8.2.7
In email, multiple images being loaded at once resulted in a performance impact. To resolve this, the fetching of inline images has been modified to use Lazy Load optimization which will retrieve file content from S3 storage on a need basis.
INC-127891 · Issue 564726
Added check for redirects when getting images from S3
Resolved in Pega Version 8.2.7
When retrieving images from S3 storage, a 303 redirect status response code was shown. Investigation showed that using a public URL caused the redirects, and this has been resolved by adding an AG hash while fetching images via an activity.
SR-D87412 · Issue 563227
Support added for multi-language email parsing
Resolved in Pega Version 8.2.7
Parsing an email body for different languages was causing performance issues. To resolve this, an enhancement has been added to support email IVA in seven languages, to use this, override the Work-Channel-Triage.pyParseReplyMail activity and add the required languages in the given parameter.
SR-D90459 · Issue 552661
Improved handling for attachments not using UTF-8 encoding
Resolved in Pega Version 8.2.7
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-D92688 · Issue 551340
Optional feature to improve pxETReport performance
Resolved in Pega Version 8.2.7
Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.
INC-175994 · Issue 667481
Removed redundant Microsoft Outlook email interaction chain
Resolved in Pega Version 8.6.2
When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.
INC-176881 · Issue 669701
Resource added to extract email threading code from message body
Resolved in Pega Version 8.6.2
In some scenarios the case ID was not being sent in the subject of email replies as expected, and the secure tracking code was part of the email body instead. That caused replies back to the email thread to create a new email interaction case instead of properly threading the new message into the conversation. Investigation traced this to some email clients removing space after the tracking code. To resolve this, an update has been made which will extract the tracking code from email-content html if it is found and otherwise fallback to the email body.
INC-178990 · Issue 664613
Added handling for reloading portal while ChatBot is active
Resolved in Pega Version 8.6.2
An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat.