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.

SR-A1345 · Issue 205768

Updated KeyManager to incorporate JVM authentication arguments for SOAP

Resolved in Pega Version 7.2

A change in the setting of secure protocol configuration (Advanced tab of Connect SOAP rule) from SSL to TLSversion 1.0 (default) was affecting two-way SSL connections to external systems that used custom implementations of KeyManager. To resolve this, com.pega.pegarules.integration.engine.internal.ssl.SSLUtils.getJREKeyManager() will consider keystores configured using standard JVM arguments: 1) javax.net.ssl.keyStoreType 2) javax.net.ssl.keyStore 3) javax.net.ssl.keyStoreProvider 4) javax.net.ssl.keyStorePassword

SR-A4515 · Issue 210886

Updated Outlook functions used by SendEmailMessage

Resolved in Pega Version 7.2

The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.

SR-A3548 · Issue 210897

Updated Outlook functions used by SendEmailMessage

Resolved in Pega Version 7.2

The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.

SR-A8788 · Issue 217912

Updated reference mapping to resolve JMS error

Resolved in Pega Version 7.2

If the Request Message Type was set to Map on the Service Tab, adding message data on the request tab to any connect-jms or service JMS rule failed to save and generated the error "Message Key value must be specified for map messages". Setting the same information on the Message Properties area worked as expected. This occurred due to improper mapping of the property references, and the mapping has been corrected.

SR-A2779 · Issue 213357

XMLSecurity library updated to ensure proper SAML STS token signature verification

Resolved in Pega Version 7.2

Classes of Repackaged version of XML Security library were conflicting with JDK/container and causing sporadic signature failures. The ApacheXMLDSig which gets registered as part of the initialization of WSS4j often conflicts with the providers with same name but loaded earlier during server startup. This has been resolved by modifying the XMLSecurity library to register the provider with a different/unique name that will not conflict with any of the standard registered providers.

SR-A1999 · Issue 214345

"Edit in Excel" not supported in Microsoft Internet Explorer 11+

Resolved in Pega Version 7.2

Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.

SR-A1999 · Issue 214460

"Edit in Excel" not supported in Microsoft Internet Explorer 11+

Resolved in Pega Version 7.2

Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.

SR-A2378 · Issue 214518

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A2378 · Issue 210254

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A2378 · Issue 211007

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

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