SR-126092 · Issue 189635
Enhanced logging for SQL exceptions with BIX
Resolved in Pega Version 7.1.8
In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.
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-126121 · Issue 189977
Improved Global Search box dismissal on iPad
Resolved in Pega Version 7.1.8
On an iPad, prforming a search with any application that shows the global search control in its header displayed a pop-up that could not be dismissed by tapping on the application below the search box. This issue occured when the script pega_desktop_AppControllerLite.js is included in the header section of the harness.To address the problem, the event binding logic for search on mobile devices has been updated to listen for a tap event instead of a click event.
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-126177 · Issue 189199
Major ruleset skim logic updated
Resolved in Pega Version 7.1.8
When skimming a ruleset to a new major version, property rules (Rule-Obj-Property) which were available in lower rulesets but withdrawn in a higher ruleset version were skimmed to the new ruleset with their status as Available. This was contrary to expected behavior, as these rules should be ignored and not added to new ruleset. This has been addressed by correcting the logic in the special handling for Rule-Obj-Property types during skimming.
SR-126181 · Issue 188742
Corrected tab display for failed visible when conditions
Resolved in Pega Version 7.1.8
When a repeating tab layout on a page group property includes "Body Visible When", tabs were displayed properly, but sections within were not being rendered for some tabs. To correct this, a visible when rule has been added to the outside content Div to handle situations where the when condition is not satisfied.
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.
SR-126361 · Issue 189663
Case Designer modified to counter Microsoft Internet Explorer 8 UI override
Resolved in Pega Version 7.1.8
While working in the Stages & Processes tab using the Microsoft Internet Explorer 8 browser, it was not possible to view or modify the step and details and some buttons were not working. This was due to the display of auto complete being overridden with the browser's UI styles z-index. To create the proper behavior, the Case-Designer-styles CSS has been modified to add a Pega-specific z-index for process entry in Microsoft Internet Explorer 8.