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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-143320 · Issue 602281

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.3.5

When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), 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-139300 · Issue 590273

Additional security for encrypted passwords

Resolved in Pega Version 8.3.5

Handling and cleanup has been updated for encrypted values to enhance security.

INC-141296 · Issue 592474

Log-access security updated

Resolved in Pega Version 8.3.5

Access control has been updated for Log-Usage class.

INC-139337 · Issue 595222

RefreshRequestors security update

Resolved in Pega Version 8.3.5

Security improvements have been added for RefreshRequestors.

INC-135349 · Issue 583004

Unit Test Ruleset rules do not count against Guardrails

Resolved in Pega Version 8.3.5

Although the documentation indicates that rules in a Unit Testing ruleset should not count against the guardrail score or unit test coverage, when branching a unit test ruleset, the branch did not carry the same unit test flag value as the source ruleset and the rulesets were counted as a result. This has been resolved with an update to ignore testrulesets in guardrail and pegaunit calculations.

INC-128923 · Issue 594162

Cross-site scripting security update

Resolved in Pega Version 8.3.5

Cross-site scripting protections have been added to OpenNoteDetails.

INC-143136 · Issue 604016

Cross-site scripting update

Resolved in Pega Version 8.3.5

Cross-site scripting protections have been updated in Designer Studio.

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 ([email protected]), 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.

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