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-A93912 · Issue 264848

SSLUtils modified to support app container keystore/truststore

Resolved in Pega Version 7.2.2

Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.

SR-A76847 · Issue 255143

Outbound Correspondence enhanced to handle Inline Content

Resolved in Pega Version 7.2.2

Pega's outbound email features previously only allowed for specifying "attachments" for inclusion for the email messages that are sent out from the Pega application and did not support "inline content". This led to all images in a Correspondence object being packaged as attachments when Pega sent Correspondence as email, and images might fail to appear in the body of outbound Correspondence when the recipient opens the message in their email client. Images intended to be part of the message body would appear as attachments to the email message. To enhance the mail services, a new PageList property "pyInlineContent" of type "Embed-EmailAttachment" has been added to the preexisting "Data-EmailAttachments" class. The "SendEmailMessage" Rule-Utility-Function has been enhanced to detect when the new "pyInlineContent" property is populated. If the email is HTML formatted, the content in the list will be given a disposition of "inline" and packaged with the HTML body in a message part of type "multipart/related" for proper consumption by email clients. If the email is not an HTML email, the "inline" content will NOT be branded as inline content, so that it appears as an attachment when the email message is opened. The "SendEmailNotification" in Pega-EventProcessing has been WITHDRAWN and replaced with a new version in SendEmailNotification which has an updated "prepare" step (#2) that puts the data for images in HTML (Corr) into the new "pyInlineContent" property of the Email Attachments page (if such a page exists), so that SendEmailMessage can process them correctly.

SR-A93295 · Issue 260100

Page-Copy given 'when' rule for assembler switch

Resolved in Pega Version 7.2.2

Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.

SR-A91393 · Issue 259616

Performance improvement for header/body mapping with ConnectSOAP

Resolved in Pega Version 7.2.2

Poor performance was seen when doing both header and body mappings to Parse XML rules from the Connect-SOAP ruleform. The order of the mappings has been reversed to allow for the the prPutAll call to be performed on the far smaller header mapping.

SR-A87950 · Issue 260162

SOAP over JMS works for JBoss EAP

Resolved in Pega Version 7.2.2

Previously, Connect-SOAP did not support the use of local resource references in Connect-SOAP over JMS in order to deploy on JBoss. These were supported in Connect-JMS. This has been fixed by adding support to create context with local resource references in the prAxisJMSTransport.jar.

SR-A102790 · Issue 271337

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A95044 · Issue 269629

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A95044 · Issue 270120

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A96815 · Issue 266585

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A96815 · Issue 269518

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

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