INC-199790 · Issue 700646
GetAllEmailWork temp page renamed to avoid conflict
Resolved in Pega Version 8.6.4
The default Email manager portal was not displaying new email triage cases. Investigation showed that because the GetAllEmailWork and CaseBreadCrumbPopulate activities were using a common name for the clipboard page "TempPage", when CaseBreadCrumbPopulate removed the TempPage clipboard page as one of its steps a null pointer exception occurred for GetAllEmailWork. To resolve this, an update has been made to rename "TempPage" to "TempPageET" for GetAllEmailWork so the names will not conflict.
INC-211417 · Issue 711611
Updated URL construction for inline images for better performance
Resolved in Pega Version 8.6.4
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-212549 · Issue 706074
HTML attachments conditionally shown in email listener cases
Resolved in Pega Version 8.6.4
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 an update to conditionally show email-content.html.
INC-214294 · Issue 710826
PopulateEmailClientWorkFilter correctly resolves field value
Resolved in Pega Version 8.6.4
The first item in the Email manager queue selection dropdown was 'DefaultWorklist', instead of 'Default worklist' or other formatted text. Investigation showed the New Page was not created for the temp results in pzPopulateEmailClientWorkFilter Activity, preventing it from resolving the customized/available field values, and this has been resolved.
INC-214367 · Issue 708410
Handling added for infinite loop in GetEmailConversations
Resolved in Pega Version 8.6.4
An infinite loop issue where a clipboard page was repeatedly added to a page list in pxGetEmailConversations was causing an out of memory condition that resulted in unavailable nodes. This has been resolved by adding boundary conditions to avoid a loop, and a fail-safe mechanism to exit an infinite loop if one does occur.
INC-214836 · Issue 709759
Handling added for infinite loop in GetEmailConversations
Resolved in Pega Version 8.6.4
An infinite loop issue where a clipboard page was repeatedly added to a page list in pxGetEmailConversations was causing an out of memory condition that resulted in unavailable nodes. This has been resolved by adding boundary conditions to avoid a loop, and a fail-safe mechanism to exit an infinite loop if one does occur.
INC-202878 · Issue 713792
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.6.5
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.
INC-211974 · Issue 706616
UpgradeInteractionCase modified to update work page on save
Resolved in Pega Version 8.6.5
After update, service cases were failing to unpend when using a custom data transform that accessed the D_CorrespondenceCase data page. Investigation showed the D_CorrespondenceCase data page was internally using the D_pxGetInteractionCaseDetails data page; this call upgraded and saved and committed the case but this commit released the lock which the custom data transform had acquired. Because this happened before accessing the CorrespondenceCase datapage, it led to an error while committing the service case details. To resolve this, the postprocessing activity "pyUpgradeInteractionCase" of D_pxGetInteractionCaseDetails has been modified to write the update on the work page as soon as a save is performed.
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.
SR-D63638 · Issue 544017
Performance improvements for opening cases with embedded images
Resolved in Pega Version 8.5
Opening cases containing email interactions was taking an excessive amount of time. This was traced to the use of embedded images, icons, etc, in the message body and signature, and was caused by the pyGetAttachmentsbyCID activity running multiple times due to discussion threads that were duplicated over and over. In some cases, more than 360 calls to the database were seen. This has been resolved by shifting some case opening processes to executing when the listener thread gets the mail, and storing the results in a .pynote property, and a URL will be used to get images instead of embedding them directly to the HTML. If preferred, this can be reverted to the previous behavior by changing the when rule (pyUseCachedHtmlForDisplay) to false.