SR-117752 · Issue 171493
Changed decimal values to comma values for NL/SE localization
Resolved in Pega Version 7.1.7
The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.
SR-119243 · Issue 175219
Changed decimal values to comma values for NL/SE localization
Resolved in Pega Version 7.1.7
The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.
SR-117805 · Issue 173117
Corrected IE handling of date picker in Report Definition custom sections
Resolved in Pega Version 7.1.7
A report definition configured to use a custom section for filtering caused a JS error in IE browsers when selecting dates from the date picker multiple times. In IE only, the DOM object containing the popup is removed from the DOM after refreshing, but the reference, _container, is not nulled. As a result, IE was trying to reuse a DOM object that wasn't present on the screen. This has been corrected.
SR-117844 · Issue 170991
Auto-refresh only available for Section Tabs
Resolved in Pega Version 7.1.7
When the "Refresh when active" checkbox was checked in a harness used in the Case Manager dashboard, creating or closing a WO did not update this page automatically. This is because auto-refresh is unsupported in the harness; it is better to use Section Tabs (the best practice statement explains why) and they are encouraged over using Harness tabs. In order to make this use clear, the auto-refresh checkbox will not be displayed in harness tabs.
SR-117847 · Issue 172996
Handling enhanced for custom system names
Resolved in Pega Version 7.1.7
If the system.name property in setupDatabase.properties was updated to reflect a custom System Name during ruleset migration, the value was not being used by the software update process and the resulting error caused a batch failure. There was a workaround of explicitly setting the system name in the field env name="Identification/SystemName" value=, but this has been updated to fetch the name from the db. In addition, the query that fetches the system name has been modified with a check to make sure that there is at least one requestor for the name it fetches.
SR-118016 · Issue 174520
Spellcheck on text area fixed for IE8
Resolved in Pega Version 7.1.7
Using IE8, a text area with SpellCheck enabled generates the error "Script Error: Message: 'null' is null or not an object" if there is more than one line present. This was caused by the handling of the check for list length, and has been modified to work with all browsers.
SR-118053 · Issue 172515
Added edit format for Designer Studio integer control in read-only when
Resolved in Pega Version 7.1.7
In the Integer Control for Designer Studio, it is not possible to set properties on the Edit Format when the presentation is ReadOnly based on a when rule. Both the Formats appear when the Edit Options is selected as Auto. Options have now been added to set the properties.
SR-118081 · Issue 169902
Focus correctly set for dynamic select using accessibility
Resolved in Pega Version 7.1.7
When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus issue.
SR-118106 · Issue 174462
Improved accessibility for UI properties
Resolved in Pega Version 7.1.7
When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it striped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue.
SR-118111 · Issue 175580
Drop-down focus modified for accessibility
Resolved in Pega Version 7.1.7
When an onChange event is set on a dropdown (select) while using the accessibility framework, the focus automatically shifted onto the next element in the UI. This was not the desired behavior, and the system has been modified.