SR-124298 · Issue 186402
SQL Merge use clarified for custom Tomcat installations
Resolved in Pega Version 7.1.8
Logic was added to ML7 to disable the SQL Merge command in environments that do not support it, but this was failing with an exception trying to parse the Tomcat name/version string if the installation was using a custom version of Tomcat and the string was not in the expected format. To handle this, the logic has been updated to to handle a custom Tomcat Name/Version string that may or may not contain version information. However, please note the following important information: The system will disable Merge if the out-of-the-box Tomcat version is detected where version If the system is using a custom Tomcat instance
SR-124384 · Issue 185899
Stream XML generation and runtime handling enhanced for optional nodes in schema
Resolved in Pega Version 7.1.8
When a stream rule was executed using connect-SOAP and blank data was passed from the UI, a tag corresponding to the XML element marked as optional was being generated. This resulted in those optional properties being unexpectedly created in source systems. To change this, the generation of the Stream XML rule has been enhanced such that at runtime it ignores optional nodes/attributes mapped to properties which do not exist or which have an empty value. NOTE: this new behavior in Stream XML rule generation is effective only with the below DSS configuration (to avoid backward compatibility issues ): Owning Ruleset : Pega-IntegrationEngine Purpose : StreamXML/DetectEmptyProperties Value : true
SR-124463 · Issue 186281
Customer Request Header mapping updated
Resolved in Pega Version 7.1.8
A Connect SOAP rule using Custom Request Headers to pass the wsse:Security, wsa:From, wsa:MessageID and wsa:Action fields was failing with the error "The server did not recognize the action which it received." Headers were mapped to a XML stream rule where the root node was mapped to a property, but the mapping was failing due to missing support to add the text node in addition to the elements. This has been fixed with code added to use getChildren() instead of getChildElements().
SR-124580 · Issue 192241
Changes made to Save preferences option in SummaryView to retain filter values
Resolved in Pega Version 7.1.8
In the reports filter section, even after clicking on save preferences button the selected filter values were not retained the second time. In the SavePreferences activity, pyAdvicetext was set to pyLabel and caused the selected filter value to not be stored. To correct this, changes were made to the SavePreferences and getPreferences activities: In getPreferences, pyAppName is set to advicetext if its length is more than zero or set to pyAppname from primary page if not. Also, in the SavePreferences activity, pyAdvicetext is set to local.adviceText (previously it was set to pyLabel).
SR-124620 · Issue 186205
Wild card support added to Elastic Search
Resolved in Pega Version 7.1.8
Elastic Search was not not working correctly for wild character search results. This was due to an error in the code and has been fixed.
SR-124631 · Issue 188702
Resolved class loading errors for XMLSignatureFactory
Resolved in Pega Version 7.1.8
Class loading issues caused errors when loading XMLSignatureFactory as an API. These have been fixed by adjusting the .jar file.
SR-124694 · Issue 186451
Added dynamic verification for XSD folder path
Resolved in Pega Version 7.1.8
An enhancement has been added to handle different URLs for schema definition XSD path in dev, test and production environments, allowing dynamic configuration of the XSD path in parse XML instead of requiring the absolute path.
SR-124747 · Issue 186549
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 truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-124751 · Issue 186945
Element substitution corrected for Parse XML
Resolved in Pega Version 7.1.8
Element substitution was not working as expected on elements properly generated in the Element Substitution section of the XML tab of the Parse XML rules. This was an error in the multi-level element substitution where the Parse XML rule didn't execute because it as expecting to find another rule which isn't needed, and has been corrected with added code to build the node path and remove clearing of substitutable elements in cases of multiple nodes configured for substitution.
SR-124751 · Issue 188572
Element substitution corrected for Parse XML
Resolved in Pega Version 7.1.8
Element substitution was not working as expected on elements properly generated in the Element Substitution section of the XML tab of the Parse XML rules. This was an error in the multi-level element substitution where the Parse XML rule didn't execute because it as expecting to find another rule which isn't needed, and has been corrected with added code to build the node path and remove clearing of substitutable elements in cases of multiple nodes configured for substitution.