INC-178148 · Issue 660924
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-188405 · Issue 673063
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
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-D81532 · Issue 544429
Corrected case-mismatch when using Top Ranked in a subreport
Resolved in Pega Version 8.3.2
Incorrect SQL Generation was seen when using the combination of Union ALL (more than 1 distinct tables) and Rank in Sub report. The sub-report had a ranking logic to pull records with greatest “pxUpdateDateTime”, but when executing the main report definition rule, Oracle responded with the error "There was a problem getting a list." Investigation showed that the query generated was not able to match the columns because they were given as pxUpdateDateTimeR1 in one and PXUPDATEDATETIMER1 in another. This only happened when display Top Ranked was selected in the subreport, and was due to Oracle being case-sensitive. This has been resolved by updating the system to get the correct column alias for rank in a subreport.
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.
INC-180184 · Issue 665091
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.7
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
SR-D41229 · Issue 513588
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.3.2
Enhancements have been added to improve the use of AWS file storage: Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS storage/class/:/enableMetrics. INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS storage/AWSSDK/metricReportingInterval. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.