SR-124700 · Issue 187999
Removed white space from edit data table
Resolved in Pega Version 7.1.8
The pop up to edit data table was displaying white space at the top left corner due to the CSS style pageTabLeft in file listvieweditor.CSS using a background-image with a width of 12px while the area to cover is 27px. This has been corrected.
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-124760 · Issue 186202
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-124868 · Issue 187837
Localization Wizard expanded to collect all applicable rulesets
Resolved in Pega Version 7.1.8
A large inconsistency was seen in the number of Strings Exported after selecting all Application rulesets and proceeding with the localization wizard depending on whether or not the top app RS were selected. The pyWorkPage.pyRuleSets page list is intended to be a list of ruleset names on which localization wizard to be executed, but only the selected first application ruleset was added. To correct this, the precondition in "GenerateRulesetList" activity has been updated to include all rulesets.
SR-124873 · Issue 187569
Updated accessibility for operator profile checkbox
Resolved in Pega Version 7.1.8
Focus was not moving to the checkbox "Operator is available to receive work" in the operator profile form when using tab control in accessibility mode. To enable this, the logic of inclusion of accessibility styles in the WorkformStyles HTML fragment has been enhanced.