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-B32592 · Issue 298344

Grid filter column localization fixed

Resolved in Pega Version 7.3.1

The repeating grid's column filter was not displaying the localized pyStatusLabel value. This has been fixed.

SR-B48351 · Issue 304587

Grid filter column localization fixed

Resolved in Pega Version 7.3.1

The repeating grid's column filter was not displaying the localized pyStatusLabel value. This has been fixed.

SR-B43325 · Issue 303149

Textarea count method updated for browser consistency

Resolved in Pega Version 7.3.1

The textarea count in Google Chrome was wrong when the textarea content was sent through form submit. When the value from TextArea is stored in the DB and then retrieved (like in a Screen-Flow), sometimes the \n character is replaced by \r\n, changing the length of the value. To ensure consistent results, the system will not consider the \r character while calculating the remaining characters length.

SR-B52664 · Issue 310856

Web mashup rendering fixed for iPhone/iPad

Resolved in Pega Version 7.3.1

The web mashup section was not rendering in iPhone and iPad due to a race condition between two network calls. Changes have been made to "PegaCompositeGadgetMgr.js" and "openCookieConsent" to delay gadget processing and resolve this issue.

SR-B52664 · Issue 312829

Web mashup rendering fixed for iPhone/iPad

Resolved in Pega Version 7.3.1

The web mashup section was not rendering in iPhone and iPad due to a race condition between two network calls. Changes have been made to "PegaCompositeGadgetMgr.js" and "openCookieConsent" to delay gadget processing and resolve this issue.

SR-B32323 · Issue 309342

Fixed SC toggling for Interaction Driver

Resolved in Pega Version 7.3.1

Two buttons on the interaction driver - 'Add Task' and 'Submit' - were freezing after more than one service case was created and the user toggled between two service cases. This has been fixed by modifying the code to handle scenarios where an onclick attribute is already present for a link.

SR-B66561 · Issue 316940

Empty grid check added to Add Item (Before) action

Resolved in Pega Version 7.3.1

Using "Add Item -> Before" to add the first row in an empty grid configured with page list as a source showed the following issues: 1. Focus was gone and not set on the first row. 2. The grid header disappeared, and the first row added appeared. 3. It was not possible to delete the first row. Even when manually clicking to set focus on the row, the system still asked for selection of the row to delete. This was traced to the "add before" function using updateHandlesAfterInsert even though the grid was empty. The postUpdate API in ui_grid.jshas been updated with a check to resolve this.

SR-B64984 · Issue 314348

Web mashup mime header set in Microsoft Internet Explorer

Resolved in Pega Version 7.3.1

When a response included the "X-Content-Type-Options: nosniff" header, the Microsoft Internet Explorer browser would not accept scripts and styles in case of mime-type mismatch. This was traced to the pzIncludeMashupScripts request not setting the mime type to text/JavaScript, and has been fixed.

SR-B49097 · Issue 308145

Validation check added for empty sections of non-template hierarchical dynamic layouts

Resolved in Pega Version 7.3.1

When a section which includes hierarchical dynamic layouts was created without a template, including an empty section for the inner dynamic layout header did not show any exception in the screen. The same use case did throw an error when using a single dynamic layout. This has been fixed by changing GridHeaderElements to not generate a call for a section include if the Section name is empty, ensuring the expected behavior of a section rule being validated and generating the error message when there are any empty sections.

SR-B44050 · Issue 319237

Accessibility improved for modal dialog errors

Resolved in Pega Version 7.3.1

When an error occurred in the modal dialog and was displayed at the top of the screen, the focus was not directed to the top of the screen to properly read the error messages for accessibility. Instead, focus shifted to the cancel button at the bottom of the screen for server side validation. To improve accessibility, code changes have been made to make the error section focusable and update the cyclic process (updating boundary elements of modal dialog) for the focus handling.

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