Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A89363 · Issue 259091

Custom DateTime control usable with declare expressions

Resolved in Pega Version 7.2.2

When a DateTime was configured to display a read-only value in Custom format and the property linked with the control had a Declare expression, the Date was initially shown with custom format during runtime, but then lost its format. During analysis, it was found that the issue was caused by Date time custom formats and Date formats not being supported as read-only for use through declare expressions. Once the screen was loaded, any further getTarget action performed by the application returned the property value of the Declare Expression without format. This has been resolved by adding logic to pass custom date time format to GetTargets to return a formatted date time string.

SR-A66960 · Issue 255162

Page error messages correctly persist with refresh harness

Resolved in Pega Version 7.2.2

When a form was submitted with missing fields, the error messages displayed to the user would intermittently disappear after a few seconds. This was caused by the getTargets activity being called after the reloadHarness, and has been resolved with a check for an empty errorFromServer value.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us