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-133026 · Issue 578278

Updated Pulse email attachment handling

Resolved in Pega Version 8.4.3

After updating from 8.3.2 to 8.3.3, the Audit Trail displayed the entire contents of an email. In some instances, attaching a .txt file caused the file extension to be displayed twice. This was due to pyNote being used to create email file posts, and has been resolved by updating the implementation to use pyEmail instead of pyNote. Backward compatibility has been ensured by still considering pyNote for older emails and changing when emails open.

INC-136264 · Issue 582470

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.4.3

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

INC-139018 · Issue 587714

Rules updated to handle Outlook change that displayed multiple/duplicate email responses

Resolved in Pega Version 8.4.3

In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.

INC-130304 · Issue 567926

Retry logic added for downloading upgraded rules

Resolved in Pega Version 8.4.3

A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.

INC-129764 · Issue 577934

Interaction case closing updated

Resolved in Pega Version 8.4.3

Utility nodes were reporting the error "Unable to close interaction case WORK-CHANNEL-INTERACTION - XXXXX." This was caused by the pxCloseExpiredInteractions activity used in ProcessEngine agent throwing a null pointer error when the Data-Channel-User has reference to a deleted interaction case. The handling for CloseExpiredInteractions has been updated to resolve this issue.

INC-133214 · Issue 590378

Deployment Manager rollback works for directed inheritance

Resolved in Pega Version 8.4.3

Rollback was not working correctly in Deployment Manager for history classes using directed inheritance. This was traced to a redundant check in AbstractHistoryPageKeeper that enforced the history pages pattern inherited from one of the base history classes, and this has now been removed.

INC-140093 · Issue 592310

Upgrade Applications Schema filtering update

Resolved in Pega Version 8.4.3

The Pega Installer was failing at Pega Rules Upgrade with an error indicating "Rules Schema assoc_data Index already exists". This has been resolved by updating the Upgrade Applications Schema to use filter for compare, but not to get custom tables.

INC-141641 · Issue 596632

Upgrade Applications Schema filtering update

Resolved in Pega Version 8.4.3

The Pega Installer was failing at Pega Rules Upgrade with an error indicating "Rules Schema assoc_data Index already exists". This has been resolved by updating the Upgrade Applications Schema to use filter for compare, but not to get custom tables.

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.

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