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-C2673 · Issue 344715

Email addresses passed intact

Resolved in Pega Version 7.4

When sending correspondence with a Bcc recipient, the Bcc recipient Email ID had the last letter removed in "populateRecipients". This has been fixed, and additional checks have been added for the other address fields as well.

SR-B34028 · Issue 329193

Resolved error message on mandatory property in grid with Microsoft Internet Explorer

Resolved in Pega Version 7.4

When using Microsoft Internet Explorer, a property marked as mandatory inside a grid layout was firing its validation when the section was loaded. This caused an error icon to appear for a mandatory column on the first row when adding a new row from an always editable grid. This was traced to focus happening twice on the mandatory column, and has been fixed.

SR-B56628 · Issue 244337

Memory leaks fixed for CPM portal with Microsoft Internet Explorer

Resolved in Pega Version 7.4

Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.

SR-B56628 · Issue 322412

Memory leaks fixed for CPM portal with Microsoft Internet Explorer

Resolved in Pega Version 7.4

Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.

SR-B64560 · Issue 334877

Memory leaks fixed for CPM portal with Microsoft Internet Explorer

Resolved in Pega Version 7.4

Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.

SR-B65958 · Issue 324162

Code modified to avoid CSS style reset on container expansion

Resolved in Pega Version 7.4

CSS styles were being reset when the container was expanded. This was an issue with the CSS class name being changed when the Expanded class name was added to the span without a space, leading to concatenation with the class name already present. A space between new(CSS class Expanded) and old class(CSS class present on span) has been added to fix this issue.

SR-B68991 · Issue 336840

Fixed Expand when evaluation for nested RDLs

Resolved in Pega Version 7.4

When using a nested repeating dynamic layouts that included section with collapsible headers, using a property pyExpanded and a custom 'when' rule isExpanded to expand and collapse the layouts and refresh the parent section from deep within the nesting was sporadically producing unexpected results. If the pagination was set on the inner RDL, after refresh the layouts were not always in the same "expanded" state as they were before the refresh. This was traced to a unique ID not being generated for the expand-indicator inside progressive loaded RDL, and has been fixed.

SR-B69968 · Issue 347332

Handling added for Google Chrome popping required field alert

Resolved in Pega Version 7.4

After tabbing into one of the required radiobutton fields but not making a selection, switching to a different application like Outlook and then switching back to the Pega user portal caused an alert popup for a required field to be thrown by the browser. This happened only when using Google Chrome and PegaWAI was included as part of the application stack. This was traced to a default Google Chrome behavior that leads to an infinite loop of invoking blur handler, and handling has been added to resolve it.

SR-B70521 · Issue 340527

Accordion stays in view when changing tabs

Resolved in Pega Version 7.4

The content in the accordion group was scrolling down below/above the screen frame when other layouts were selected. This was an issue with the accordion not being in viewport when opened since the content was hidden using display:none, and has been fixed by calling scrollIntoViewIfOutOfView for active accordion. ScrollIntoViewIfOutOfView is defined in pzpega_ui_doc_domUtils.

SR-B71597 · Issue 330030

JAWS reads shortcut labels with custom controls

Resolved in Pega Version 7.4

JAWS was not reading the modal dialog title and some inside content for GDIT. This was due to JAWS only reading the value and not the label for pyShortcutTitle and pyShortcutDescription as they are displayed using a custom control. To fix this, the system will use formatted text for pyShortcutTitle and pyShortcutDescription when pxRequestor.pyPegaDesignMode != 'true'.

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