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-A101514 · Issue 317772

Busy indicator memory leak fixed for multiple iframes

Resolved in Pega Version 7.3.1

A memory leak was found with the client side script busy indicator when multiple iframes were involved. As part of this change, a part of the code in pega_ui_busyindicator.js which removes the status div within hidden iframes has been reworked to avoid memory leakage.

SR-B64971 · Issue 316298

Added alt text attribute to paperclip icon for accessibility

Resolved in Pega Version 7.3.1

A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.

SR-B14710 · Issue 288487

Accessibility added for down arrow button access

Resolved in Pega Version 7.3.1

Accessibility has been added to the tooltip on a button when it is accessed via Down Arrow key so it will be read by JAWS.

SR-B52773 · Issue 312408

Improved null/blank parameter handling when using Microsoft Internet Explorer.

Resolved in Pega Version 7.3.1

After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.

SR-B52773 · Issue 312968

Improved null/blank parameter handling when using Microsoft Internet Explorer.

Resolved in Pega Version 7.3.1

After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.

SR-B70481 · Issue 322272

Scrollbar works when text area disabled

Resolved in Pega Version 7.3.1

After upgrade, scroll bars were disabled when a text area is disabled. This was traced to code that stopped the scrolling due to the disabled text area CSS style pointer-events being set to "none", and has been fixed by adding the needed CSS in the py-enduser71-workarea-overrides.css file.

SR-B70481 · Issue 322427

Scrollbar works when text area disabled

Resolved in Pega Version 7.3.1

After upgrade, scroll bars were disabled when a text area is disabled. This was traced to code that stopped the scrolling due to the disabled text area CSS style pointer-events being set to "none", and has been fixed by adding the needed CSS in the py-enduser71-workarea-overrides.css file.

SR-B44811 · Issue 304937

Non-standard container support added for harness refactoring

Resolved in Pega Version 7.3.1

After upgrade, some harnesses for sections mentioned in a container were not displayed correctly. Adding a new container and then including the same section or recreating the harness worked as expected. This was an issue with the system considering the pyTabbedHeader property even for non-standard type layouts during harness generation refactoring, and has been fixed with added code in processHarnessContainers method (of HarnessAssemblyStreamSupport.java) to set bAccordionHeader and bTabbedHeader to false when pyContainerType is not standard.

SR-B68818 · Issue 318268

Corrected section refresh when target section is not in DOM

Resolved in Pega Version 7.3.1

An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.

SR-B68818 · Issue 316252

Corrected section refresh when target section is not in DOM

Resolved in Pega Version 7.3.1

An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.

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