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-A8491 · Issue 221433

Improved property panel response speed

Resolved in Pega Version 7.2

Poor performance was seen with some complex sections in the user application if the amount of data sent to the client for a property panel was > 2MB.This section has been tuned for greater responsiveness.

SR-A9930 · Issue 220782

Corrected modal flow submitted by ActionAutoSubmit

Resolved in Pega Version 7.2

ActionAutoSubmit was not working correctly with modal windows, incorrectly submitting the flow action from which the modal was invoked and not submitting the main flow. This has been fixed.

SR-A9886 · Issue 221957

JAWS access added for 'Currently Open' tab menu

Resolved in Pega Version 7.2

Screen readers were not speaking the label when focus was given to the tablist menu. This was caused by a missing aria attribute on the anchor tag, and has been corrected.

SR-A10041 · Issue 219306

Ampersand retained is passed parameter

Resolved in Pega Version 7.2

The ampersand character (&) was being removed when included as part of the parameter chain even though the flow was executed. This was caused by the URL decoder, and a check has been added to ensure proper handling.

SR-A7951 · Issue 218577

Sort filtering updated for Repeat Grid using RD as source

Resolved in Pega Version 7.2

Using the Sort functionality as a filter was not working in a Repeat Grid where records were fetched using a Report Definition. This was due to the property passed to the RD function not being populated while generating unique values in the filters, and parameter values have now been added to the visible list if the column name is a function in pzGetGridColUniqueValues activity.

SR-A11321 · Issue 223010

Check added to allow inheritance control overrides

Resolved in Pega Version 7.2

If a property used "inheritfromproperty" as the control, the choice of "select on blur" was not being retained when the action was submitted. This was traced to settings in the inheritance overriding the action, and a check has been added to ensure the format will not persist if the control is changed or is empty.

SR-A6245 · Issue 220858

Restored visibility to activity parameters in the navigation rule

Resolved in Pega Version 7.2

When an activity with parameter name "flowName" was added in the navigation rule as an action, this parameter was not present in the navigation rule. This was an issue where changes had been made to not show the parameter with the name "flowName" in the configuration of the runactivity action of the Service Level Agreement rule, but that change was affecting the complete runActivity action. To correct this, the pzGetRuleParameters activity has been updated to get the form type from the toplevel page and set it using the fromClassType parameter, allowing it to be used along with existing conditions.

SR-A7687 · Issue 218670

Red highlighting reinstated for required fields in repeat grids

Resolved in Pega Version 7.2

Required Field Names in a repeat grid were not turning red as expected when validation failed. This was a change from previous behavior and the highlighting has been reinstated for clarity of use.

SR-A11172 · Issue 222988

RuleSet Pagination fixed in DS

Resolved in Pega Version 7.2

When first launching the ruleset stack landing page in Designer Studio, the second page of the paginated list was not accessible. If either the "next" link or the "2" link were clicked, the page did not respond (and no network activity was shown in the browser's network tab). Clicking on any other page link worked as expected, and refreshing the browser (or not expanding a ruleset item in the list) caused the second page to be accessible. The problem was due to the handling of password fields in the call to getQueryString, and has been updated to correct this.

SR-A8647 · Issue 218523

Handling added for grids sourced with data pages

Resolved in Pega Version 7.2

If a grid layout was used to show a user worklist and the source of the grid layout was a Data page populated from a Report Definition, the result had a join that resulted in a page list having embedded pages of the joined class. This was due to the Page and Classes not being defined properly, and better handling has been added.

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