SR-125455 · Issue 189496
Error handling improved for importing data instances
Resolved in Pega Version 7.1.8
When importing data instances from a file, messaging showed success even when importing failed due to a database error (e.g.. column length not sufficient). In addition, the error in the log file was not detailed and no error appeared on screen. This problem was specific to Oracle DB and only with Unicode characters with a column size exceeding maximum length of 256. The error handling in this case has been improved: if there is a data base error, a message will appear on the modal dialog and all the changes in the transaction will be rolled back.
SR-125497 · Issue 188946
Handling added for undesignated authentication
Resolved in Pega Version 7.1.8
If service package was unchecked, it was not possible to call authenticated activities from the service activity and errors were generated stating "You lack access required to execute RULE-OBJ-ACTIVITY @BASECLASS". To resolve this, changes have been made in the service layer to bypass authentication for all services that do not have authentication enabled on their service packages.
SR-125561 · Issue 188136
Modified processing to handle SOAP requests with text mapping
Resolved in Pega Version 7.1.8
Headers like action or MessageID with addressing information were not being added to authentication that used a SOAP service with Enable ws-addressing on. This was traced to headers with only text mapping not working with latest axiom jar, and the code has been modified to process the text node.
SR-125810 · Issue 188388
invokeHttpConnector updated to support TLS
Resolved in Pega Version 7.1.8
In order to support connections to TLS-enabled endpoints with Connect-HTTP, the invokeHttpConnector Activity has been updated.
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.