Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D87188 · Issue 551349

Mentioned user in Pulse correctly converted to hyperlink

Resolved in Pega Version 8.3.3

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-D92688 · Issue 551339

Optional feature to improve pxETReport performance

Resolved in Pega Version 8.3.3

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.

SR-D63638 · Issue 544015

Performance improvements for opening cases with embedded images

Resolved in Pega Version 8.3.3

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.

SR-D81707 · Issue 544671

Webchat bot interaction box cleared on submit

Resolved in Pega Version 8.3.3

After upgrade, when using Google Chrome responses to webchat bot questions were not getting cleared from the chat input window after the enter/send button was clicked. This has been resolved by changing the order of refresh section and set value and disabling submit on refresh when refreshing pzSubmitArea.

SR-D86837 · Issue 547992

Webchat interaction timeout updated

Resolved in Pega Version 8.3.3

Interaction timeout was not working as expected in Webchat channels. This was traced to the system looking for total interaction timeout instead of user inactive timeout, along with the Web chat interaction case clipboard page being stale. To resolve this, timestamp propagation has been updated for pxProcess in Work-Channel-Interaction.pxAcquireInteraction.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us