SR-A6949 · Issue 216721
Revised class display properties to avoid looping
Resolved in Pega Version 7.2
When running Service Wizard using the setting 'Service Purpose for Rule-InsProd-Product', the browser would become unresponsive while attempting to display the properties. This was traced to a displayed properties loop caused by creating service from the service wizard and specifying a class name which has siblings and a parent class containing a page of the child class. To avoid this condition, a check has been added to handle cases where if a page class is descendant of the class which contains the page, the properties of that page will not be displayed.
SR-A8207 · Issue 216601
RuleGenerator updated to handle same-name JSON fields
Resolved in Pega Version 7.2
Connect-Rest wizard was throwing a StackOverFlow error while creating elements. The issue occurred during data transform generation when there was a same name JSON field in the nested structure. Changes have been made to RuleGeneratorREST and RuleGeneratorCommon to handle this use case.
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-A5183 · Issue 213803
Added check to ensure all invalidated shortcuts are processed correctly
Resolved in Pega Version 7.2
When running SQL server version 2012 with a particular JDBC driver, executing a DML statement without setting the pyMaxResultCount caused the number of records returned to be limited by the default record size, and the system was not picking up the latest versions of all of the rules after shortcuts were invalidated. To resolve this, the method invalidateShortcuts(RACacheAppCentricImpl) has been modified to set pyMaxRecords to zero when calling executeRDB so that all the impacted rows are processed.
SR-A5233 · Issue 212884
Added external DB support for DB2 v.8
Resolved in Pega Version 7.2
After upgrade, trying to connect to DB2 ver 8 as an external database generated the error "SQLCODE: -4700 SQLSTATE: 56038 Cannot connect to DB2". This was due to Method getSchemaName(SQLGeneratorDB2) firing a query which is valid only on a higher/supported version of DB2. To accommodate other versions of the database, the system will fallback to the V8 syntax if the higher-level query fails.
SR-133085 · Issue 210184
DATE support added for SQL
Resolved in Pega Version 7.2
Support has been added for using the Date column type with SQL servers in cases where the DB supports the DATE type.