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-A4931 · Issue 214295

Restored focus highlight for post-error Harness Treenavigation

Resolved in Pega Version 7.2

A highlighting error occurred in Harness Treenavigation7 when moving between assignments if an item failed validation. This has been corrected.

SR-A7482 · Issue 220320

Reset validation activity for deferred loading with alternate page context

Resolved in Pega Version 7.2

If a section was configured to use a defer load activity and the page context was set to something other than the defer load activity class, the defer load activity was not visible when attempting to set the pre-load activity and an error was generated. This was caused by a change to the defer load activity validation that pointed to the using page class instead of the previously used section class. The validation has now been reset to to use the section class instead of using page class in order to support rendering on a different page.

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.

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