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-A11400 · Issue 223194

Corrected JAWS reading hidden label

Resolved in Pega Version 7.2

When using accessibility mode, a label was read during screen navigation using the keyboard tab when the label was hidden on the screen display. To correct this, the ARIA label has been updated to consider whether or not aria-hidden="true".

SR-A9842 · Issue 220353

Fixed Rule Compare in DS

Resolved in Pega Version 7.2

After upgrade to an intermediate release it was found that the menu_script bundle was not loading, leading to issues with attempts to run DesignerStudio > System > Refractor > Compare Rules -> Rule Type of Property. A call to the missing scripts has been added, and the section 'pyRuleSelection1' has been modified to use the current format.

SR-A9233 · Issue 219215

DateTime control updated for variable month length

Resolved in Pega Version 7.2

When the datetime property was configured to use the timeframe format (i.e. 2 Days 5 Hours ago format), the value was not getting accurately calculated when the date value was more than 31 days from the current date. This was due to flawed logic in considering the length of the month (defaulting to 31 days) and has been updated to calculate the days correctly based on calendar information.

SR-A12107 · Issue 222923

Fixed Header background gradient rendering in Google Chrome

Resolved in Pega Version 7.2

The "Header background" mixin was rendering gradients incorrectly on Google Chrome by treating the starting color and end colors in opposite ways. The style has been fixed to render as expected on all browsers.

SR-A11742 · Issue 222780

API updated for Dropdown sourced with data page

Resolved in Pega Version 7.2

When the load behavior is "At Screen Load (Default)", the dropdown control did not display the values from the sourced data page. The same data page used as a source for a Radio Button worked fine. This was an issue with the timing of the data loading: the values in the data page must be loaded prior to the screen rendering, and the API has been updated with a check to ensure proper behavior.

SR-A9481 · Issue 221843

Cancel of modal window clears clipboard

Resolved in Pega Version 7.2

When a modal was launched but then canceled before the fields were filled in. submitting the main form generated a validation error on the fields that were no longer present / relevant. This was due to the modal fields persisting on the clipboard, and the logic has been updated to clear the validation messages if the cancel button is clicked or there is a click outside.

SR-A8132 · Issue 216840

Validation repeat added for dropdowns with auto-refresh

Resolved in Pega Version 7.2

Field level errors (red highlights) were appearing incorrectly in cascading dropdowns on values that had been correctly selected. This was caused by the automatic refresh configuration causing client-side messages to be lost, and has been corrected by performing validation again on the reloaded cell.

SR-A1275 · Issue 207203

Stopwatch icon fully visible for LogOffTimer

Resolved in Pega Version 7.2

The code used to display the stopwatch icon used in the LogOffTimer HTML dialog has been updated so the icon is fully visible in a modal window.

SR-A9861 · Issue 219782

Access Key on buttons is clickable

Resolved in Pega Version 7.2

The hot key character on a button caption was not clickable due to a missing 'data-click' attribute. This has been fixed.

SR-A12703 · Issue 224986

Optimized browser performance with large grids

Resolved in Pega Version 7.2

Large amounts of data on screen in grids caused performance issues when submitting the flow action. This was traced to a large repeated number of JS calls to a getAttribute function, and the function has been optimized to resolve 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