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-B5678 · Issue 277570

Fixed out of bounds issue for deleting nested grid row

Resolved in Pega Version 7.3

An IndexOutOfBoundsException was generated when trying to delete a row in a nested grid. This was due to an incorrect base_ref being generated by the tools.getActive function for the second cell because the first cell also had a grid. To fix the issue, the cell generation has been changed to use tools.getStepPage instead.

SR-B5982 · Issue 279431

Tabbed form submission errors read by JAWS

Resolved in Pega Version 7.3

JAWS was not reading the error messages on the screen if the form submission was in a tabbed layout. To correct this, a setTimeout has been added to the reloadAcessibility function to call displayErrorTable.

SR-B6575 · Issue 277285

Filter popup made more efficient for large number of parameters

Resolved in Pega Version 7.3

The filter pop-up was not fully loading when the grid source has a very large number of parameters. To resolve this, the request fired in the popover initiation has been changed to pass the paramList in postData and decode it while setting params in step 2 of pzGetPopOverData.

SR-B6683 · Issue 275694

Tab layout focus corrected for "show next error"

Resolved in Pega Version 7.3

The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.

SR-B6992 · Issue 277289

Fixed default first record focus in modal repeating grid with Internet Explorer 11

Resolved in Pega Version 7.3

After upgrade, it was observed that when a repeating grid layout is opened in a modal window, the first record was selected or focused by default when using Internet Explorer 11. This has been fixed by adding a check for accessibility.

SR-B7143 · Issue 281865

Div fixed for Add button using GridAction section include

Resolved in Pega Version 7.3

After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.

SR-B8469 · Issue 278141

RTE linkbox input handling corrected for modal windows

Resolved in Pega Version 7.3

In an "inline editable" grid with 'click to edit' selected, clicking on the RTE link inputbox in the modal window caused the grid row to be submitted as if the click took place outside the grid. The gridEventHandler has been updated to correct this.

SR-B8495 · Issue 279313

SVG image support added

Resolved in Pega Version 7.3

Support has been added for previewing and searching for SVG type images.

SR-B8744 · Issue 279872

OnClick passes parameters to DT from inside a grid

Resolved in Pega Version 7.3

The OnClick event was not passing its parameters to a Data Transform or activity if it was inside a grid due to the property not being generated with its full reference. This has been fixed by modifying pzActionAppendValue to generate the complete property reference instead of just the property name.

SR-B9137 · Issue 267865

RD column context menu alignment fixed

Resolved in Pega Version 7.3

On a report definition with many columns, scrolling to the right caused the column context menu to not be aligned with the column. The menu alignment code calculations have been modified to correct this.

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