INC-212549 · Issue 706072
HTML attachments conditionally shown in email listener cases
Resolved in Pega Version 8.8
When Rich text/html (non-plain text) emails were ingested in email, the original mail was not getting added to the case. Investigation showed that the pzCreateTriageWork activity had an explicit delete step to remove any attachment that started with 'email-content'. Since the HTML attachment name starts with 'email-content', it was deleted in above activity. This has been resolved by adding a when rule named 'pyLinkEmailTriageContentHTML' which will conditionally show email-content.html.
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-211417 · Issue 711612
Updated URL construction for inline images for better performance
Resolved in Pega Version 8.8
System slowness was seen, and inline images were not getting displayed when the case was opened. This has been resolved by modifying pyExtractHtmlFromAttachment to ensure the image source URL is built in a consistent way whether or not there is a cache to call from.
INC-146544 · Issue 604495
Updated handling for unexpected character set in non-UTF-8 email
Resolved in Pega Version 8.4.4
After upgrade, the listener properly created a case from an email, but the space character was being replaced by ? in the inbound emails. Investigation showed the messages did not appear properly in the UI if the email was sent using any encoding other than Unicode (UTF-8) and it had a special character set. To resolve this, the system will remove the attachment type which includes the charset.
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.
INC-185455 · Issue 671977
Email widget auto-refreshes for incoming email
Resolved in Pega Version 8.7
The email thread was not updated automatically for incoming email in an email interaction case with Outlook, but did refresh when the work object was closed and opened in perform mode. This was traced to a Jump statement after pyMapEmailToEmailTriage which interfered with threading, which has now been removed.
INC-232672 · Issue 742205
PreChatQuestions correctly captured in history
Resolved in Pega Version 8.8
When a chat was escalated to the agent, an internal error message was shown after the queue position and wait time message. The PreChatQuestions flow was executed, but the questions were not captured in the pyHistory of BotCase. This was traced to an incorrect reference relating to inbound and outbound messages and has been corrected.
INC-239086 · Issue 746010
Menu titles allow HTML formatting
Resolved in Pega Version 8.8
Attempting to format line breaks and hyperlinks within the menu titles was not taking effect. This was due to the system only accepting a string and stripping out HTML tags in menu titles. To support this formatting use, an update has been made which will not strip the tags on the platform side but will instead send the formatted text all the way to the messaging layer for the menu title inside a menu message type.
INC-229423 · Issue 729987
forcemigratetriagecases added to allow check migration status query skip
Resolved in Pega Version 8.8
The IsMigrationDone query was taking around 20 seconds to run on a very large amount of data in pc_work table. To address this, a new 'when' rule pyforcemigratetriagecases has been added to allow skipping checking migration status for on-demand migration.