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.

INC-142930 · Issue 600769

Email history will be stripped from case replies

Resolved in Pega Version 8.5.2

When sending an email reply to a case, the entire email history (all previous emails in the email chain) was attached to the case as part of the reply.To resolve this, updates have been made so the system will strip history only when it's a follow-up mail. In addition, an issue with duplicate attachments has been corrected, and attachments from trailing mail will not be copied to a new post.

INC-143320 · Issue 602279

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.5.2

When attempting to enter a email with a hyphen '-' in the domain part of an email ID (, the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.

INC-145425 · Issue 600773

New email template added to include full message history

Resolved in Pega Version 8.5.2

Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.

INC-146544 · Issue 604493

Updated handling for unexpected character set in non-UTF-8 email

Resolved in Pega Version 8.5.2

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-150367 · Issue 606028

Double quotes escaped in entity mapping

Resolved in Pega Version 8.5.2

A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.

INC-120299 · Issue 578183

Added null check to ActivityStatusExceptionHandler

Resolved in Pega Version 8.5.2

Invalid Parameter Exceptions were being logged in the production environment related to an 'CPMInteractionPortalWorkArea' execution error on page 'pyTmpDisplayHarness' indicating "Invalid value for aReference passed to, char)". This has been resolved by adding a null check before reading the DC data model in the activity ActivityStatusExceptionHandler.

INC-128279 · Issue 591378

Layout Group tab alignment correctly shown in Microsoft Internet Explorer

Resolved in Pega Version 8.5.2

Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.

INC-132176 · Issue 588809

Cache cleared before PDF generation to ensure proper fonts

Resolved in Pega Version 8.5.2

The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.

INC-132219 · Issue 580266

Values with accent characters are sorted properly

Resolved in Pega Version 8.5.2

Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.

INC-132569 · Issue 595174

Resolved case detail overwrite

Resolved in Pega Version 8.5.2

In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us