SR-A12107 · Issue 222923
Fixed Header background gradient rendering in Google Chrome
Resolved in Pega Version 7.2
The "Header background" mixin was rendering gradients incorrectly on Google Chrome by treating the starting color and end colors in opposite ways. The style has been fixed to render as expected on all browsers.
SR-A11742 · Issue 222780
API updated for Dropdown sourced with data page
Resolved in Pega Version 7.2
When the load behavior is "At Screen Load (Default)", the dropdown control did not display the values from the sourced data page. The same data page used as a source for a Radio Button worked fine. This was an issue with the timing of the data loading: the values in the data page must be loaded prior to the screen rendering, and the API has been updated with a check to ensure proper behavior.
SR-A9481 · Issue 221843
Cancel of modal window clears clipboard
Resolved in Pega Version 7.2
When a modal was launched but then canceled before the fields were filled in. submitting the main form generated a validation error on the fields that were no longer present / relevant. This was due to the modal fields persisting on the clipboard, and the logic has been updated to clear the validation messages if the cancel button is clicked or there is a click outside.
SR-A8132 · Issue 216840
Validation repeat added for dropdowns with auto-refresh
Resolved in Pega Version 7.2
Field level errors (red highlights) were appearing incorrectly in cascading dropdowns on values that had been correctly selected. This was caused by the automatic refresh configuration causing client-side messages to be lost, and has been corrected by performing validation again on the reloaded cell.
SR-A1275 · Issue 207203
Stopwatch icon fully visible for LogOffTimer
Resolved in Pega Version 7.2
The code used to display the stopwatch icon used in the LogOffTimer HTML dialog has been updated so the icon is fully visible in a modal window.
SR-A9861 · Issue 219782
Access Key on buttons is clickable
Resolved in Pega Version 7.2
The hot key character on a button caption was not clickable due to a missing 'data-click' attribute. This has been fixed.
SR-A12703 · Issue 224986
Optimized browser performance with large grids
Resolved in Pega Version 7.2
Large amounts of data on screen in grids caused performance issues when submitting the flow action. This was traced to a large repeated number of JS calls to a getAttribute function, and the function has been optimized to resolve this.
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.