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.

SR-A12980 · Issue 227344

Added dropdown to select applications for new requirements

Resolved in Pega Version 7.2.1

A dropdown has been added to the Requirements screen to display the existing applications for the current user when creating new requirements.

SR-A20072 · Issue 238701

Portal markup in PDF resolved

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.

SR-A20094 · Issue 238591

Localization handling updated for High Level Overview documents generated in Word

Resolved in Pega Version 7.2.1

In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.

SR-A20183 · Issue 238612

Localization handling updated for High Level Overview documents generated in Word

Resolved in Pega Version 7.2.1

In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.

SR-A21569 · Issue 242079

Corrected persistence of deleted requirements links with multiple actors

Resolved in Pega Version 7.2.1

When checking in a specification with more than one actor specified on it, deleted requirement links re-appeared after the rule was closed and re-opened. This was due to an unnecessary section refresh, which has been removed.

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