SR-A86896 · Issue 259785
Column filters appear on horizontal iPad
Resolved in Pega Version 7.2.2
When a grid was configured with enough columns to require a horizontal scroll bar, scrolling to the right and trying to filter on the right side columns did not show the filter popup on an iPad in Horizontal orientation. The expected behavior is that the popup would appear near the column the user filtered. This was seen in iPad Safari due to hardware acceleration, and has been corrected with the inclusion of a CSS rule and the popover JS to trigger reflow for popover loader.
SR-A86896 · Issue 259811
Column filters appear on horizontal iPad
Resolved in Pega Version 7.2.2
When a grid was configured with enough columns to require a horizontal scroll bar, scrolling to the right and trying to filter on the right side columns did not show the filter popup on an iPad in Horizontal orientation. The expected behavior is that the popup would appear near the column the user filtered. This was seen in iPad Safari due to hardware acceleration, and has been corrected with the inclusion of a CSS rule and the popover JS to trigger reflow for popover loader.
SR-A76192 · Issue 254055
Added support for tabbing on fixed size freeze header in grid
Resolved in Pega Version 7.2.2
When a grid was configured with many columns and the Freeze Header checkbox was selected from the presentation tab, clicking the header and pressing tab caused the header to move and lose alignment with the columns below. This was an unexpected use case, and support for tabbing on a Fixed size Freeze header in a grid has been added.
SR-A24208 · Issue 247087
Fixed dropdown filtering logic
Resolved in Pega Version 7.2.2
When a grid was configured with source as pagelist and cells with dropdowns as controls in it, attempting to filter the dropdown list displayed the filter window instead of the options in dropdown. This was caused by the filter logic not considering the filter by value setting and using the pyUILabel property by default for showing the unique values in the filter pop-up. To correct this, the system will consider the value of pyShowFilterUIBy while also allowing certain controls to maintain their format.
SR-A95224 · Issue 262257
Fixed dropdown filtering logic
Resolved in Pega Version 7.2.2
When a grid was configured with source as pagelist and cells with dropdowns as controls in it, attempting to filter the dropdown list displayed the filter window instead of the options in dropdown. This was caused by the filter logic not considering the filter by value setting and using the pyUILabel property by default for showing the unique values in the filter pop-up. To correct this, the system will consider the value of pyShowFilterUIBy while also allowing certain controls to maintain their format.
SR-A87970 · Issue 255816
New window alert shows with accessibility mode
Resolved in Pega Version 7.2.2
When a new harness was opened in an "accessible" mode, the new window alert was not thrown when opening the new window in a pop-up or when opening in a new tab. This has been fixed.
SR-A89711 · Issue 257213
New window alert shows with accessibility mode
Resolved in Pega Version 7.2.2
When a new harness was opened in an "accessible" mode, the new window alert was not thrown when opening the new window in a pop-up or when opening in a new tab. This has been fixed.
SR-A85709 · Issue 255759
Cleared erroneous dirtycheck popup on DropDown using lazyload
Resolved in Pega Version 7.2.2
When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.
SR-A77307 · Issue 260263
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.
SR-A77307 · Issue 260728
Null check added for selectNodes extraction
Resolved in Pega Version 7.2.2
When an assignment contained a field with custom control that included 'ClientValidation' with 'Activate input formatting' selected for this field, attempting to change the field or submit the assignment generated the JS error 'Unable to get property 'selectNodes' of undefined or null reference'. This has been resolved by adding a null check to the selectNodes extraction function to handle empty values for the returned object.