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.
SR-124760 · Issue 185307
Corrected timing for change action on autocomplete
Resolved in Pega Version 7.1.8
When a Data Transform was configured on an autocomplete to clear properties, the DT fired on load of the section itself and caused inconsistent behavior depending on timing. This was a case of the generation not honoring the "Run data transform" option available in the section include property panel, and has been corrected.
SR-124820 · Issue 187585
Changed calendar implementation for parse XML
Resolved in Pega Version 7.1.8
A parse XML record processing a calendar date prior to 1582 (Jan 1, 0001) was returning an incorrect date after conversion. This was traced to a routine that assumed that a date was of type Julian if it was before 1582, causing a Gregorian date prior to 1582 to be unexpectedly converted to Julian. To correct this, the implementation that parses the XML for date, datetime, and time has been changed to joda time.
SR-124833 · Issue 187240
Added null check for datetime in SOAP
Resolved in Pega Version 7.1.8
Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.
SR-124882 · Issue 186524
Cookies only generated if IAC enabled
Resolved in Pega Version 7.1.8
IAC cookies were being generated in environments where IAC was not deployed, causing the application to present the error "Browser cookies must be enabled for PRPC Internet Application Composer to function." This problem only occurred with the Google Chrome and Firefox browsers. To correct this, the system has been updated to bypass cookie generation if IAC is not in use, adding a condition to bypass the cookie detection logic in PegaCompositeGadgetMgr.js if pega.web.config.encrypt is set to false.