SR-A12357 · Issue 225139
Improvement made to UI error message persistence
Resolved in Pega Version 7.2
Error messages were being cleared from the UI even when they were present on the clipboard. This made it difficult to isolate the error in data entry screens with many fields, leading to confusion and multiple submits to regain the error messages. This has been resolved by updating the loadtabcontents method to pass the pzKeepPageMessages parameter.
SR-A13963 · Issue 227442
Dropdown control updated for Apple mobile Safari
Resolved in Pega Version 7.2
The Apple mobile Safari webview displayed a problem with updating the state of selection in a dropdown, creating scenarios where two values were shown as selected or previously selected values were lost. This was traced to the DOM selector "option:selected" selecting multiple options by accumulating all of the selections done by the user up to that point in time. The databinder function has been modified to handle this specific environment for dropdowns.
SR-A12915 · Issue 225381
Error messages remain visible with GetTargets
Resolved in Pega Version 7.2
If there were error messages (page-set-messages or property-set-messages) and the GetTargets activity was called on the page, the error messages disappeared. This was traced to the pzKeepPageMessages's request header value being false, and the "callGetTargets" method has been updated to pass pzKeepPageMessages parameter.
SR-A13446 · Issue 225382
Consistent width for GenerateDatePicker validation messages
Resolved in Pega Version 7.2
Due to a problem with the inclusion of the GenerateDatePicker error message div in the control's span markup, any validation message had inconsistent widths. This has been fixed.
SR-A11550 · Issue 222998
State abbreviations will not be localized
Resolved in Pega Version 7.2
A dropdown sourced from a datapage that contains region abbreviations was incorrectly localizing the US state abbreviations for entries such as Indiana ("IN") to be lowercase ("in"). By default the dropdown options are localized, but a check has been added to bypass default localization if the source is a Field Value.
SR-A11170 · Issue 222267
State abbreviations will not be localized
Resolved in Pega Version 7.2
A dropdown sourced from a datapage that contains region abbreviations was incorrectly localizing the US state abbreviations for entries such as Indiana ("IN") to be lowercase ("in"). By default the dropdown options are localized, but a check has been added to bypass default localization if the source is a Field Value.
SR-A5880 · Issue 216627
Updated error label highlighting for reused sections
Resolved in Pega Version 7.2
The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.
SR-A8520 · Issue 217466
Updated error label highlighting for reused sections
Resolved in Pega Version 7.2
The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.
SR-A12012 · Issue 224390
Update to Localization Wizard Correspondence and Paragraph rules
Resolved in Pega Version 7.2
When updating the Language pack, Correspondence and Paragraph rules will not be picked up in a localization wizard run when the rules were present in a previous version and not updated in the new version. This is a change from previous behavior where the expected delta version was not correct as it included the previous version's Paragraph and Correspondence rules.
SR-A12012 · Issue 223008
Update to Localization Wizard Correspondence and Paragraph rules
Resolved in Pega Version 7.2
When updating the Language pack, Correspondence and Paragraph rules will not be picked up in a localization wizard run when the rules were present in a previous version and not updated in the new version. This is a change from previous behavior where the expected delta version was not correct as it included the previous version's Paragraph and Correspondence rules.