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-A7611 · Issue 217142
Ampersand not rendered properly for DropDown
Resolved in Pega Version 7.2
In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.
SR-A1440 · Issue 213844
Added catch for unspecified layout format
Resolved in Pega Version 7.2
Layouts saved without a format name were not rendering correctly; the container format was changed to 'other', which generated an exception due to the 'other' format not being available in the XML. To prevent this error, the layout format assignment is now wrapped in the JS with a try-catch.
SR-A3540 · Issue 210203
Added check for duplicate Date Control validation error
Resolved in Pega Version 7.2
In a screen flow, it is possible to move forward despite validation errors on the Date control. However, returning to the control caused the validation error message to be displayed twice. This was caused by both the server side and the client side generating the error. To correct this, logic has been added to check if the clipboard already has the messages defined in pClientErrors and avoid adding them to the clipboard if so.
SR-A6010 · Issue 215099
Added handling for special characters in RUF labels API
Resolved in Pega Version 7.2
A change in the handling of special characters such as quotation marks was causing compiler errors after upgrade. This was traced to the StringUtils.escapeIntoJavaString api for label generation in generateCellContent RUF and has been corrected.
SR-A6636 · Issue 215085
Added missing hover text for closing work object
Resolved in Pega Version 7.2
Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.