SR-A11179 · Issue 225127
Expandable rows editing corrected for Repeat Grids in Microsoft Internet Explorer
Resolved in Pega Version 7.2
Editing a Repeat Grid row with row with 'Expandable rows' enabled caused the Microsoft Internet Explorer browser to hang. Using 'Modal dialog' for the row editing worked as expected. This was caused by the GetIndex function incorrectly interfacing with the ExpandPane, and has been fixed.
SR-A10468 · Issue 220902
Default Value handling improved for properties on grids
Resolved in Pega Version 7.2
Given a Data Page of class X-Data-Y and a grid in a section of a class X-Work-Y, it was possible to set a property reference as 'Default value' for any of the columns in repeat grid and build expressions using properties of class X-Data-Y. However, when the page was saved, it searched for the properties in X-Work-Y and generated an error. To correct this, the section pzCell_DefaultValue_Field has been updated to have two versions of the default value, one for in a grid and another for when not in a grid. The default value will show properties from the parent class context. In addition, as the default value for cell inside a grid is picked from parent context, a property reference of Section Class can be specified as 'Default value'.
SR-A11329 · Issue 222587
Fixed popup navigation menu scrolling
Resolved in Pega Version 7.2
When a button was configured to pop up the navigation menu on click, the menu was fixed on the screen even after scrolling the screen up and down. This was caused by a div inconsistency in the function split button constructor method(SplitButton), and has been fixed.
SR-A12533 · Issue 226150
Touchstart support added to mobile menus code
Resolved in Pega Version 7.2
Touchstart was not working as expected on mobile configurations using the previous style of menus. Support for Touchstart events has been added to the menubar code.
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.