SR-120780 · Issue 178357
Corrected text input focus highlighting for accessibility
Resolved in Pega Version 7.1.8
When using an accessible application, the fields with pxTextInput control were not highlighted on focus. This has been corrected.
SR-120781 · Issue 177810
Changed close modal icon text for JAWS
Resolved in Pega Version 7.1.8
If focus is given to the X icon on the modal dialog, JAWS was reading "Unlabeled 2 Button." In order to indicate that it is the Close modal icon, the title="close modal" has been added to the modal dialog's X button.
SR-120809 · Issue 180066
Clarified clipboard API mapping of "null" JSON values
Resolved in Pega Version 7.1.8
In order to support JSON where optional properties with unknown values are included and set to null (rather than being omitted), the API method ClipboardPage.adoptJSONObject has been updated to omit occurrences of null in the JSON source rather than setting them to a text value of "null" for that property on the clipboard.
SR-120876 · Issue 185865
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-120876 · Issue 183543
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-120946 · Issue 180460
Ensured custom formats for dynamic layouts appear consistently
Resolved in Pega Version 7.1.8
Custom formats for Dynamic Layouts in an application skin were not appearing after upgrade. This was caused by stale code related to alignment issues, and has been resolved.
SR-121048 · Issue 192690
Corrected dynamic select refresh behavior
Resolved in Pega Version 7.1.8
When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.
SR-121105 · Issue 180175
Corrected text wrapping for attached notes
Resolved in Pega Version 7.1.8
When using out-of-the-box functionality for attaching a note, the text was not wrapped and showed in one long line. The root cause of this problem was the "pre" tag in the HTML not breaking the lines and not wrapping, and styles have been added to fix the attachment issue.
SR-121115 · Issue 183812
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.
SR-121115 · Issue 182793
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.