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-136264 · Issue 582472

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.5.1

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 587715

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

Resolved in Pega Version 8.5.1

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.

SR-D85563 · Issue 551684

Dependencies of module.xml documentation update

Resolved in Pega Version 8.5.1

Documentation has been updated to include specifics about adding a dependency in Microsoft JDBC Driver 6.0., under dependencies of module.xml.

SR-D88570 · Issue 550104

Cleanup script topic moved to Post-Upgrade steps in deployment documentation

Resolved in Pega Version 8.5.1

The deployment guides have been updated to indicate that the cleanup script should only be run after the upgrade has been completed, as well as clarifying that this is only required if the clean up scripts have never been run previously.

INC-152776 · Issue 621244

Check added for HTML and linefeed combined in email

Resolved in Pega Version 8.5.3

In the Interaction right hand pane Email triage widget, additional line breaks were seen when displaying email message data that contained table tags. This was a missed use case for email which contains both HTML and '\n', which resulted in the system replacing '\n' with </br>. This has been resolved by adding a check whether the content has HTML tags which will avoid the replacement.

INC-156422 · Issue 617382

Updated email triage case creation to avoid unique key issue

Resolved in Pega Version 8.5.3

After upgrade, when the email listener queued the case and an agent picked up the queued item to create an Email Triage Case and then the interaction case, trying to commit the case failed with a Unique Key violation. Investigation traced this to the system trying to insert the record into the PC_WORK_TRIAGE table twice due to a timing issue in the workobject commit. This has been resolved.

INC-143925 · Issue 597289

Documentation update to alternate URL for mobile build

Resolved in Pega Version 8.5.3

The documentation located at https://community.pega.com/knowledgebase/articles/mobile/85/setting-alternative-host has been updated to reflect current information and instructions for setting an alternative host.

INC-139018 · Issue 587716

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

Resolved in Pega Version 8.6

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-142930 · Issue 600768

Email history will be stripped from case replies

Resolved in Pega Version 8.6

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 602280

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.6

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