INC-152776 · Issue 621244
Check added for HTML and linefeed combined in email
Resolved in Pega Version 8.5.3
In the Interaction right hand pane Email triage widget, additional line breaks were seen when displaying email message data that contained table tags. This was a missed use case for email which contains both HTML and '\n', which resulted in the system replacing '\n' with </br>. This has been resolved by adding a check whether the content has HTML tags which will avoid the replacement.
INC-166844 · Issue 651407
Email bot updated to handle negative and positive feedback on the same text
Resolved in Pega Version 8.7
When positive and negative training was done on the same piece of text, text extraction by Email Bot failed. For example, when using the sentence. “John Smith plays cricket”, the bot detects “John” as person name. If user wants to train the bot to detect “John Smith” as the entity, the user needs to first remove “John” and build the model, and then select “John Smith” and build the model again. In this case, the email bot never again detects “John Smith” as person name due to the negative feedback given for “John”. This was traced to the entities having same the startIndex/endIndex, and has been resolved by removing entities of the same modelName which have the pyIsRemoved property as true so that multiple entity models are detected on the same word.
INC-181267 · Issue 663666
Enhancements added to support Pega-SocialDocuments with Case Archival
Resolved in Pega Version 8.7
Attachments can be added using the Recent content widget create Pega-SocialDocuments or Link-Association-Documents, but Case Archival only supported Link-Attachments. This resulted in Pega-SocialDocuments that were not visible when viewing the archived case. This has been resolved with an enhancement to support PegaSocial-Document attachments to a case: - Internal as well as external PegaSocial-Document attachments are archived - For external PegaSocial-Document attachments, only the reference is archived - Both kinds of attachments are retrieved and displayed (either the file or reference to the file) by the ArchivalReview harness - Attachments are downloadable - The exposed properties of the attachment are visible - If the social document is attached to multiple cases, then after archival of one case, the other live cases will continue to have access to that social document. Please note that while a PegaSocial-Document can be created independently and does not need to be attached to a case, this enhancement to Case Archival does not support that use case.
INC-192646 · Issue 679065
Correct class for properties set by Chatbot
Resolved in Pega Version 8.7
After initiating a service case from legacy webchat and subsequently resolving the case using DX API V1, additional properties with a different applied-to class than that of the workclass were added to the service case workpage while setting answer values to the question structure from the @baseclass.pxSupplyAnswerToQuestion API. Open assignments on the case could be submitted through the portal without any issues but validation errors occurred when the same assignment was completed though DX API, e.g. from a custom React frontend. This has been resolved by moving the properties to baseclass or Work- class as appropriate.
SR-D87188 · Issue 551350
Mentioned user in Pulse correctly converted to hyperlink
Resolved in Pega Version 8.5
In the Interaction portal, mentioning a user in Pulse using @ was not converting the name to the user name with hyperlink for Email Interactions. @ mentions were working as as expected in Phone Interactions. This problem was introduced as part of using OWASP to sanitize HTML user input in Rich Text support, and was due to OWASP converting @ to an HTML entity. To resolve this, the @ will be excepted from HTML conversion.
INC-179888 · Issue 663846
Training data correctly added to model
Resolved in Pega Version 8.7
Negative training data was not getting added to the entity model. This was traced to logic used to remove consecutive spaces which was incorrectly removing new lines and leading to entity detection of entities such as address line. This logic has now been removed.
INC-184902 · Issue 669453
Corrected portal image display for authenticated request
Resolved in Pega Version 8.7
Email images for the user portal were not displayed in the browser but were showing correctly in the manager portal. The URL to the image was the same in both cases, however for the user portal the URL request was requiring authentication. This has been resolved by updating the API to use currentsessionURL.
INC-170135 · Issue 652525
Rich HTML handling added for outbound email
Resolved in Pega Version 8.7
The HTML content was visible in the received email when replying from the email pane in the existing email interaction. This has been resolved by adding logic to handle rich HTML for outbound email.
INC-190417 · Issue 675213
ModifiedGetEmailPosts data transform to better handle very large messages
Resolved in Pega Version 8.7
Blank emails were seen when the message was over 4000 characters. This was traced to an issue with initializing param.index2, and has been resolved by modifying the pxGetEmailPosts data transform to take param.index2=0 out of the loop for large emails.
INC-189819 · Issue 676594
Entity highlight corrected
Resolved in Pega Version 8.7
In the email channel, the entity value highlighted under "Training" tab was different from the actual value detected. The location where it was detected was also different. This was traced to an inconsistency of the title shown on the UI of training data tab, and has been resolved by updating the title shown on each entity as well as using exit iteration instead of skip step in pyStructureEntity.