INC-157214 · Issue 631600
Mentioned user in Pulse appears correctly
Resolved in Pega Version 8.6
When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.
INC-160372 · Issue 629922
Resolved unneeded chat survey error logging
Resolved in Pega Version 8.6
After configuring a chat server to do a post chat survey, the post chat survey was correctly served but errors indicating "Cannot find PegaCA-Work-SurveyNPS.Thank you for your feedback. van type Rule-HTML-Paragraph" were logged. This was caused by the method used by the system to distinguish between text and paragraph questions in pyProcessNextStep, and has been resolved by adding additional checks for whether paragraph exists before opening it.
INC-160688 · Issue 632230
Skip topics from the attachments setting honored
Resolved in Pega Version 8.6
Topic detection was happening for attachments even when it is disabled in the UI. This issue was traced to pyTopics which were not properly configured by selecting checkboxes in iNLP configuration for Email Channel, and has been resolved.
INC-165188 · Issue 635775
Third-party links allowed to pass target attribute in anchor
Resolved in Pega Version 8.6
Attempting to connect to Docusign, a third party application, via Email in an interaction portal was not working, and the error "account.docusign.com refused to connect" appeared. This was caused by the HTML data being sanitized so the attribute 'target' was not allowed to pass and the application could not open in a new tab. To resolve this, an update has been made that will allow the target attribute for an anchor tag.
INC-165886 · Issue 637242
JWT token support added for Digital Messaging
Resolved in Pega Version 8.6
An enhancement has been added to support the use of JWT tokens for authentication with the Digital Messaging API.