SR-125975 · Issue 194136
XMLTreeViewBuilder enhanced to support default value passing for XSD
Resolved in Pega Version 7.1.8
When running the Connector & Metadata Wizard, the generated XML Stream rule did not include the default value defined in XSD. To correct this, support has been added for default value in XMLTreeViewBuilder so it will be passed to XML stream and parse rules.
SR-126110 · Issue 189593
Adjusted custom header SOAP handling
Resolved in Pega Version 7.1.8
When a Soap connector request has custom headers, the values of the headers were blank; the tags were getting populated but with blank values in-between. This as an issue with the configuration under Rule-Connect-SOAP for the recent enhancement AddCustomHeadersToSoapEnvelope, and has been corrected.
SR-126156 · Issue 190077
Random ID generation changed to use OpenSAML
Resolved in Pega Version 7.1.8
In certain cases, SSO setup with SAML 2.0 failed with the message "Unable to process the SAML WebSSO request: Unable to process SAML2 Authentication". The error was due to the generated ID being sent with a "+" character in it which could not be handled smoothly. To avoid this issue, the system has been changed to use the OpenSAML API instead of using UUID when generating random IDs for all types of WebSSO requests.
SR-126157 · Issue 193349
Email Listener message handling updated for DSN messages
Resolved in Pega Version 7.1.8
Signature protected emails were causing an error even when the 'include DSN messages' checkbox was active. According to the Oracle tech note at http://www.oracle.com/technetwork/java/javamail/faq/index.html#imapserverbug this can be worked around by creating a new copy of message for this call, and that code has been added to this function.
SR-126414 · Issue 189748
Static content retrieval corrected
Resolved in Pega Version 7.1.8
StaticContent was not being cached by the browser for all HTTP responses that came from the remote nodes via FCM/IAC. Instead, every request resulted in a full round trip to the server, causing performance problems for end-users. As part of a recent change, the trailing slash after the thread was removed from the initial request sent from the browser to Gateway to avoid the retrieval of static content for every thread. However, the gateway code slash was appended after the thread for the subsequent requests. This has been corrected.
SR-126432 · Issue 189500
Enhanced SQL error logging
Resolved in Pega Version 7.1.8
In order to better understand and address sporadic "Unexpected error during processing" SQL errors, logging has been added to capture the exception message when classloading from database fails. The changes are done in AbstractJdbcJarReader and the loggers are of level ERROR and will be logged to Appserver log files.
SR-126719 · Issue 189646
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the trust store where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126775 · Issue 189860
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-127799 · Issue 192294
Included CMIS library updated
Resolved in Pega Version 7.1.8
Using Connect-CMIS Rule form, attempting to get a list of Repositories from a CMIS Server that allows Web service binding with Basic Authentication was failing with 401 - Unauthorized error. The getRepository operation succeeded when using SOAPUI or Apache Chemistry CMIS client Workbench. This was a defect with the particular CMIS library version included with Pega 7.1.7, and has been corrected by updating to a revised version.
SR-127838 · Issue 194007
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.