SR-A8595 · Issue 218942
Security updated for SAML Rule keystores
Resolved in Pega Version 7.2
Password encryption has been updated for the Keystores records used by SAML Rule forms for signing and decryption in the auth service rule data.
SR-A6223 · Issue 214939
Resolved WSDL SOAP exception when using target namespace
Resolved in Pega Version 7.2
When adding a well-defined XML ParseRule as a Request Header, saving and checking in the rule caused the Deployment results link to generate the error "Caught exception while creating WSDL for service package: : com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException Header message is included with method namespace instead of targetnamespace" This was an error in the code handling a target namespace for Request Headers (configured on the Service Soap -> Requests tab), and has been fixed.
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-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-A9136 · Issue 221836
Added loop avoidance when Service SOAP wizard encounters parent class with sub-pages
Resolved in Pega Version 7.2
The Service SOAP wizard was presenting properties as Input Parameters that appeared to have a repeating reference not actually present in the Data Class specified to process. The initial reported issue showed the wizard presenting Input Parameters such as "RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1...." increasing in length on each line. This was caused by a loop created while creating the service from the Service Wizard and specifying a class name which has siblings and a parent class containing pages of the child class. To avoid this, the system will break the loop if the parent contains the page property of the child class.
SR-A5103 · Issue 214155
Improved Rule-Connect-SOAP connector performance
Resolved in Pega Version 7.2
Performance issues seen when running Connect-SOAP with NTLM authentication and tracing it using Performance Profiler have been resolved by modifying the parsing to improve use of the cached objects.
SR-A7518 · Issue 219402
EJB Connector wizard fetches fully qualified class names for compile
Resolved in Pega Version 7.2
When using a JNDI Server referencing remote EJBs, configuring Connect EJB through the wizard resulted in compilation errors. This was due to incorrect wrapper class generation, and the generation has been updated to use fully qualified class names.
SR-A11696 · Issue 224612
Namespaces considered while constructing WSDL type maps
Resolved in Pega Version 7.2
Previous versions that had repeating complex elements used as references ended up with "type2" appended to those elements when the WSDL was generated after upgrade. This format was put in place to avoid namespace collisions when duplicate names are used for the same complex types in a schema with different targetnamespace. However, even though the WSDL was semantically correct, it caused backward compatibility when generating stubs out of WSDL and created the need to regenerate the stubs. To resolve this, changes have been made to XMLTreeViewUtils.addDocElementDeclaration() to consider namespaces while constructing the type definition map.
SR-A7804 · Issue 218676
Rest inbound call mapping updated to determine response type
Resolved in Pega Version 7.2
When Rest service was built in the Pega application and exposed to external applications (non-Pega), the JSON request payload was not mapped to the clipboard during the input data mapping if the setting "Content-Type: application/json; charset=utf-8" was used, but did work as expected when the client calling the service used "Content-Type: application/json" and did not set charset. This error was linked to a space character missing between the given Content-Type value and charset parameter, and has been updated to avoid this issue in the future by setting the extract content-type value and excluding the charset parameter value, then determining whether the response is of text type.