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-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-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-124919 · Issue 188505
Handling added for invalid event object in Dynamic Select
Resolved in Pega Version 7.1.8
When there are two DynamicSelect controls in a section, the value selected in the first causes the list of choices in the second to be filtered. If there is an invalid but non-null event object, selecting a value in the first dropdown generated the JavaScript error "Member not found". This has been resolved by adding a condition in the reload API to handle the non-null invalid object.
SR-124930 · Issue 186906
Inserted validation for reversed availability dates
Resolved in Pega Version 7.1.8
In Developer portal-> administrator -> profile -> availability , entering UnavailableFrom and To dates for the schedule where the From date is in the future of the To date was submittable without triggering error messages. The root cause of the issue was a skipped activity step. The validation step is looped only for specific embedded pages, and was not being called in this case. This datetime error has been corrected.
SR-124971 · Issue 188628
Button type filter added to Report Browser
Resolved in Pega Version 7.1.8
After navigating to the Report Browser and then back to another tab, clicking on any input field and clicking enter caused the columns filtering pop-up to appear even if the user was not on the Report Browser tab. This issue only occurred with the FireFox browser due to FireFox treating elements as the 'default action' of the form and using them as submits, causing a press of the enter key to fire off the onclick event for those buttons. In order to correct this, the type='button' attribute has been added to the filter
SR-125028 · Issue 187645
List View filter corrected
Resolved in Pega Version 7.1.8
When enable filtering is turned on in the display fields, the ListView filter tab failed to retrieve the record. This was traced to the Keycode 32(space bar) being conditionally added in pega_ui_listview, and has been corrected.
SR-125042 · Issue 193350
Corrected decimal field validation for special characters
Resolved in Pega Version 7.1.8
The '&' symbol was not being parsed correctly when entered into a decimal field. This was a tooltip issue with the ampersand character when the harness setting was set to full error text, and has been resolved.
SR-125044 · Issue 187842
Ampersand(&) handled as text and not parameter for data transforms
Resolved in Pega Version 7.1.8
When passing a parameter to a data transform, if the parameter value contained an ampersand ('&') or certain other non alphanumeric characters, an error was generated (visible in tracer) and the task failed. This was a case where an '&' character was not not handled as literal text, causing the RunActionWrapper to explicitly parse it and create params out of it. There was a local-change solution to directly reference a property value containing the required text value instead of passing it in via a parameter, but the system has been updated to encode ampersand(&) in the file pzpega_ui_events.