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-A9324 · Issue 222377

Check added for post value check boxes and radio buttons

Resolved in Pega Version 7.2

When post value was configured on text field, adding check box and radio buttons caused the text field to disappear. A context page parameter check has been added to correct this issue.

SR-A7616 · Issue 217425

Option added to change CKEditor default fonts to pts vs pxs

Resolved in Pega Version 7.2

The RTE Font control was hard-coded to a font-size value given in pixels instead of points. This caused confusion when mail composed in CKEditor (which uses pixels) was displayed in Outlook (which uses points). To better handle these differences, an extension point has been provided to allow overriding CKEDITOR.config.fontSize_sizes in UserWorkForm.CKEditor to set font sizes from px to pt as desired.

SR-A8800 · Issue 220963

Corrected header collapse/expand on clicking menu navigation

Resolved in Pega Version 7.2

If a section include had the "Display header title" checkbox selected and then included a button on the title with an Onclick event to open the Menu with navigation, clicking on the button opened the Menu with options as expected, but clicking on any option would expand or collapse the header. This has bene corrected.

SR-A10406 · Issue 223580

Check added for page context when dropdown used in nested repeating grids

Resolved in Pega Version 7.2

A Dropdown placed in nested repeating grids with the event request onclick action "Post value" disappeared from the DOM on select of an option. This was due to an incorrect page parameter, and a check has been added to send the correct contextPage.

SR-A9326 · Issue 220214

JAWS reads non-truncated workbasket name

Resolved in Pega Version 7.2

In the dashboards, workbaskets with long names have the truncated text shown on the screen as "...". JAWS was reading this as dot dot dot instead of the entire text, which was not expected behavior. This has been corrected by the adding role and aria-label to the span containing the description, and the value of the aria-label will be retrieved from another attribute containing the complete workbasket name.

SR-A9512 · Issue 219314

Accessibility enhancements added to autocomplete

Resolved in Pega Version 7.2

Autocomplete was only being read out if accessibility was turned on at the access group level. The implementation of the autocomplete control is now accessibility-checkbox independent, and the custom messages "Reached the beginning of the list" and "Reached the end of the list" have been added for clarity.

SR-A11522 · Issue 224442

Smart tip popup placement corrected for scrolling screen layout

Resolved in Pega Version 7.2

While hovering the mouse, the icon smart tip was misplaced and displaying at different XY positions if the harness contained a screen layout and the browser showed a scroll bar. This has been corrected.

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.

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