SR-125751 · Issue 194311
Updated scroll bar generation for rule forms
Resolved in Pega Version 7.1.8
Calling WBOpen in a list view on click event allows a pop up to show. For rule or data instances which have forms bigger than the pop up size, no scrollbar was shown. This was caused by the previous ruleset regulating the scrollbar, RuleFormFrameset, being marked as deprecated but not removed from the function. To replace this rule, Window.open Attributes resizable and scrollbars have been set to true.
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-125910 · Issue 194305
Corrected data population in report for exposed column
Resolved in Pega Version 7.1.8
Data was not being populated in a report for an exposed column when it was dragged and dropped from the data explorer of Report Editor. This was caused by the CreateColumnPage fieldName being hard-coded to Param.FieldName for embedded page properties, and has been changed to set FieldName conditionally.
SR-125937 · Issue 190307
Aligned Connector lines in Process Modeler
Resolved in Pega Version 7.1.8
Upon opening a flow rule, the Connector lines in Process Modeler were rerouted inconsistently with what was the saved state of the rule. The root cause was traced to code defects that resulted in the incorrect display of an error message and the incorrect drawing of the connector lines when the process modeler is loaded. These have been corrected.
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-126335 · Issue 192177
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.
SR-126335 · Issue 194307
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.