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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B48146 · Issue 305146

CheckedOutRulesBulk updated with null check

Resolved in Pega Version 7.3

The MyCheckedOutRulesBulk ruleset was taken as null for operators with rule checkout disabled, causing them to see all the non-rule resolved classes as private edits. To correct this, additional criteria have been added to fetch records only with pyClass starting with 'RULE-' and the List views MyCheckedOutRulesBulk and MyCheckedOutRulesBulkPM have been changed to check for null values.

SR-B509 · Issue 277331

Turkish characters supported in autocomplete filtering

Resolved in Pega Version 7.3

Support has been added for Turkish locale special characters in autocomplete filtering.

SR-B5224 · Issue 277207

Fixed intermittent override default template failure

Resolved in Pega Version 7.3

The override default template was displaying inconsistent behavior due to the fromLocalAction function not correctly resetting. This has been corrected.

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-B6428 · Issue 280748

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

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.

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