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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C69729 · Issue 414920

Improved security for XXE

Resolved in Pega Version 8.2

Several updates have been made to improve security against External Entity Injection.

SR-C72385 · Issue 414867

Resolved ClassCast email exception caused by duplicate javamail class loading

Resolved in Pega Version 8.2

A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders.

SR-C77994 · Issue 419283

Resolved ClassCast email exception caused by duplicate javamail class loading

Resolved in Pega Version 8.2

A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders.

SR-C77107 · Issue 417088

Added check for sending email attachments with XML data

Resolved in Pega Version 8.2

When using SendEmailNotification to send an email with an attachment, the attachment was added but had no content when the email was received. In this case, if the property pyRemoveXML was true and if the email attachment content had XML data and did not contain a <pagedata tag, then the removeXML() method was returning "" as the email attachment content. This has been fixed by adding a check so if the property pyRemoveXML is true and if the email attachment content has XML data and doesn't contain the <pagedata tag, then it will return the original content itself.

SR-C52077 · Issue 402334

Corrected currency format for it_IT locale

Resolved in Pega Version 8.2

For few locales, the formatting API was returning the number with leading white space. This caused the localeNumFormat to not be properly set. To correct this, the leading space will be trimmed before creating the 'localeNumFormat' parameter.

SR-C78402 · Issue 417490

Added Page clear messages for Record Editor to clear stale errors

Resolved in Pega Version 8.2

An error message appeared correctly if the validation failed after editing a record, but refreshing the row caused the error message to be removed. The same error message appeared again if any filter was applied on any column. This has been fixed by adding Page clear messages in post and pre activities of pzRecordEditor.

SR-C79302 · Issue 416824

Added backwards compatibility for ValidateDelete in Records Editor

Resolved in Pega Version 8.2

Due to a missed use case, ValidateDelete was not being called from the new records editor. This has been corrected by adding the step to call ValidateDelete in pzDeleteRecord activity.

SR-C79306 · Issue 417259

Visibility consition added for checkbox used to skip validation for rules import

Resolved in Pega Version 8.2

An enhancement has been added to show or hide the the validation checkbox in Import Wizard by way of the new property 'pyDisableSkipValidate'. This adds a visibility condition for the checkbox used to skip running rule validation in pzImportRecords.

SR-C79941 · Issue 416721

Corrected JSON for eventType DisableOperators in the security event log

Resolved in Pega Version 8.2

An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.

SR-C80084 · Issue 417238

Target connectivity preference updated in Revision Manager to address deployment error

Resolved in Pega Version 8.2

Using the deployment page to deploy a revision or migrate it to a target environment was failing. This has been resolved by correcting the target connectivity preference in the connector rules.

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