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.
SR-124910 · Issue 192169
Parse XML handling added for blank page list data
Resolved in Pega Version 7.1.8
In some very specific data scenarios, the auto-generated multiple parse XML routine for rules off of a WSDL import failed in a manner that was silent to the application but was visible in the logs. This happened with nested page list parse XML configurations with an apply rule where the data of page list of first page was empty, causing the mappings of the page list in other pages to be skipped even though the data was there. If the page list data of the first page was not empty, there was no error. To resolve this, code has been added to check the resolved path in the XML content instead of the unresolved.
SR-124910 · Issue 192293
Parse XML handling added for blank page list data
Resolved in Pega Version 7.1.8
In some very specific data scenarios, the auto-generated multiple parse XML routine for rules off of a WSDL import failed in a manner that was silent to the application but was visible in the logs. This happened with nested page list parse XML configurations with an apply rule where the data of page list of first page was empty, causing the mappings of the page list in other pages to be skipped even though the data was there. If the page list data of the first page was not empty, there was no error. To resolve this, code has been added to check the resolved path in the XML content instead of the unresolved.
SR-124952 · Issue 189563
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-124952 · Issue 189565
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-125070 · Issue 186577
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".