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 600770

Email history will be stripped from case replies

Resolved in Pega Version 8.4.4

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 602282

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.4.4

When attempting to enter a email with a hyphen '-' in the domain part of an email ID (test_ab@test-email.com), 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 600774

New email template added to include full message history

Resolved in Pega Version 8.4.4

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 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-149667 · Issue 610053

Email Triage properly maps attachments to case

Resolved in Pega Version 8.4.4

Attachments from emails coming in via the Email channel were not being attached as expected to both the Email Triage case and the case generated from that. Instead, attachments were only being added to the triage case. This was traced to the pyAttachments property not being properly updated for attachment to the generated case, and has been resolved.

INC-150367 · Issue 606030

Double quotes escaped in entity mapping

Resolved in Pega Version 8.4.4

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-140279 · Issue 597756

JMX logging added to upgrade diagnostics

Resolved in Pega Version 8.4.4

In order to improve diagnostic information, infoForced loggers have been added for debugging upgrade issues related to JMX calls to enable and disable rules creation.

INC-144555 · Issue 603071

Changelog cleanup added for de-optimized properties

Resolved in Pega Version 8.4.4

Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.

INC-144869 · Issue 606617

Improved ScalarPropertiesWriter logging

Resolved in Pega Version 8.4.4

In order to improve diagnostics, debug loggers have been added to ScalarPropertiesWriter.java to print column name in the logs while creating map between column names and their values from clipboard page.

INC-146595 · Issue 604791

Initialized entryName for light weight inventory instance

Resolved in Pega Version 8.4.4

When running deployment on a new pipeline created for the next minor version, once the deployment process got to the point of showing aged updates, the “view aged updates” came back as blank screen. Viewing the logs showed the aged update elements come back but were missing the pyName associated with them. Investigation showed that the system did not have support for setting the mEntryName for LightweightInventoryInstance objects. This has been resolved by adding a junit to ensure that getEntryName() doesn't return as null and should be equal to pzInsKey.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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