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-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 (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-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.

SR-D47795 · Issue 524674

Fallback to Pulse notification added for empty incoming account in CallEmailAutomation

Resolved in Pega Version 8.3.2

After upgrade, issues were seen with the sender receiving email notifications for sent messages when alias addresses were used for incoming emails. To resolve this, a fallback mechanism to use a Pulse notification has been added in cases where an incoming email account is not found in the pyCallEmailAutomation activity.

SR-D48246 · Issue 518689

TextAnalyzerClass will be populated during upgrade if not present

Resolved in Pega Version 8.3.2

After upgrading, the email channels were failing to process the emails and the error "Unable to load data page D_pyEntityClassMapping. Required parameters : ClassName cannot be blank" was seen in the tracer log. Analysis showed the email channels were failing to process the emails due to the pzUpgradeVersion property in Data-Channel-Email instances being inconsistent post-upgrade. To resolve this, the system has been updated so if the TextAnalyzerClass or name property is not present in old email channels (created in 7.4), it will populate that property in the upgrade activity with the default classname.

SR-D49782 · Issue 518047

Extension point added for ClearInteraction to support custom interactions

Resolved in Pega Version 8.3.2

In order to support clearing a custom interaction page after clicking the "Reset" button on preview console, an extension point has been added to pyClearInteraction.

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