SR-131504 · Issue 200712
Localization added for 'save' label in Calendar popup
Resolved in Pega Version 7.1.8
The label 'Save' in the Calendar popup has been made available for localization.
SR-131600 · Issue 199942
Modified Accordion display of alerts
Resolved in Pega Version 7.1.8
Validation messages in a section with accordion and UI elements were overlapping with Accordions below. This has been corrected by modifying the script to include the alert message.
SR-131611 · Issue 201761
Currency field 'save draft' function updated
Resolved in Pega Version 7.1.8
Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.
SR-131613 · Issue 199443
Focus set on RTE after reload section with Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
On GCS Support Portal using the Microsoft Internet Explorer browser, switching the Note Type to Internal set the focus on textarea, but switching the same to External did not set the focus on RichTextEditor (RTE). The setItemFocus API has been updated to correct this.
SR-131625 · Issue 200677
Added option for validating read-only fields
Resolved in Pega Version 7.1.8
Validation was occurring on read-only fields, causing unexpected behavior. This is now a configurable option to display error messages on read-only fields that is available at the control level and cell property panels, with a default of 'false'.
SR-131648 · Issue 201958
Resolved element focus issue for Microsoft Internet Explorer with required field
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer browser, tabbing or clicking to the next field after the previous field is designated as Display value using read only formatting generated an error message that the field cannot be blank. An internal blur was getting fired on refocusing an element in Microsoft Internet Explorer, and a check has been added to the pzpega_ui_events.js file.
SR-131816 · Issue 200787
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-132002 · Issue 201652
Resolved date format changing with Microsoft Internet Explorer refresh
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer browser, the date format DD-MMM-YYYY was losing its format after refreshing or applying a validation rule or Data Constrain rule. The GenerateDatePicker logic has been updated for Microsoft Internet Explorer to correct this.
SR-132106 · Issue 200970
Decimal separator issues addressed for Microsoft Internet Explorer 9 and German locale
Resolved in Pega Version 7.1.8
Using the Microsoft Internet Explorer 9 browser and the German locale setting, the comma decimal separator was lost following several refreshes and the value was multiplied by the unanchored digits. In case of format type is "number" and "Display value using read-only formatting" enabled, the input type is generated as text but data-value was still being set with a clipboard value instead of localized value. This generation has been changed to a formatted value as data-value attribute on the input element to fix the issue. Please note that this will address customer configuration where "Display value using read-only formatting" is enabled. If this option is not enabled, the input will continue to be generated as a number and in such cases refreshes with separators may not work and can't be fixed due to browser limitation/behavior for input type number.
SR-132677 · Issue 201726
Resolved decimal property validation error
Resolved in Pega Version 7.1.8
On validation, an extra space was being added to a decimal property which then caused the validation to fail. This was caused by the pzPerformGridAction activity calling the ProcessAction activity with a new parameter page which was not receiving the inStandardsMode parameter value from the original request, leading pzGenerateFormat to assume that the browser is in Quirks mode. This has been fixed.