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-124763 · Issue 188692
UpgradeOnOpen style sheet handling corrected
Resolved in Pega Version 7.1.8
The UpgradeOnOpen activity was run each time a harness was opened on the Developer Portal. This was inefficient, but also caused some manual UI changes to revert on the refresh due to the style sheet being incorrectly reset by the UpgradeOnOpen activity. This 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.
SR-124875 · Issue 186361
Event firing fixed for blank Start and End values
Resolved in Pega Version 7.1.8
As a result of changes made to better handle cases when distributed search is enabled and "Work indexing" is enabled, events were no longer firing for existing and new events where there where Start and End dates were not set. This has been fixed.
SR-124877 · Issue 186909
Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.
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.