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-B5450 · Issue 274669

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-B5618 · Issue 281402

Autocomplete works in grid layout

Resolved in Pega Version 7.3

If a data transform was in the data class and the same was used as a source for the autocomplete inside a repeat grid, the data was not present in runtime. The configuration did work if the data was in the work class. This was traced to missing context, and has been fixed by ensuring the pre-datatransform and pre-activity have the grid row page context.

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-B6161 · Issue 275612

RD generating checkbox control as T/F image fixed

Resolved in Pega Version 7.3

A report definition was not showing checkbox controls as images for true/false properties when generated automatically. This has been fixed.

SR-B6292 · Issue 276738

New accessibility control for adding explicit text to RB column headers

Resolved in Pega Version 7.3

In order to create report browser column headers with explicit text for accessible users, a new available control named pyReportBrowserControl that uses the parameter "Type" has been added to the pzRBShortcutsGrid7 section.

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.

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