SR-A13307 · Issue 226543
Encoding corrected for "+" in localization
Resolved in Pega Version 7.2
When the Localized Label in pyStatusLabel included a "+" (plus sign), it is displayed as "+"in Microsoft Internet Explorer and Google Chrome). This was due to the 'Pending Approval+1' label being encoded twice, and has been fixed.
SR-A12529 · Issue 224775
Microsoft Internet Explorer 11 rendering properly without requiring compatibility setting
Resolved in Pega Version 7.2
After upgrade, the Work User portal was not rendered properly in Microsoft Internet Explorer 11 unless the Compatibility View was enabled. Compatibility has now been set in the framesetuser code to handle this rendering.
SR-A8574 · Issue 218907
"When" handling improved for expanding repeating layout sections
Resolved in Pega Version 7.2
Given multiple records in a Dynamic Repeating Layout, it was not possible to implement a 'When' rule that would expand the last record while collapsing all prior records. This was due to the parameter name used by the expand header function being the same for all sections in a Dynamic Repeating Layout. In order to support more robust layouts, the system has been updated to better handle setting parameters to evaluate the 'When' condition for sections inside repeating layouts.
SR-A12640 · Issue 225253
Error icon display corrected for large tabbed layouts
Resolved in Pega Version 7.2
The Error Icon was shown correctly in a tabbed layout of up to 9 tabs, but for 10 or more tabs, the 10th tab error icon was not displayed at all, and the error for the 11th tab was displayed on the 1st tab. This was traced to a logic error regarding the tab element index, and has been corrected.
SR-126885 · Issue 193150
Check added to avoid multiple submits from custom controls with refresh
Resolved in Pega Version 7.2
After upgrading, double-clicking on a custom control button with a refresh harness caused a form to be submitted multiple times and an exception was generated. A check has been added to avoid multiple submits of the same form.
SR-A12648 · Issue 225025
Localization restored for pyCaption (backwards compatibility)
Resolved in Pega Version 7.2
After upgrade, the sub case of a work object was not being translated using pyCaption field value. Using pyLabel field value worked as expected. This was a backward compatibility issue, and localizing on pyCaption or property value has been restored for use.
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.