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.

INC-162763 · Issue 646109

Case creation and Save As performance improvements

Resolved in Pega Version 8.7

Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.

INC-192979 · Issue 677696

Case creation and Save As performance improvements

Resolved in Pega Version 8.7

Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.

SR-B81365 · Issue 332518

Enhanced security for IAC gadget

Resolved in Pega Version 7.4

The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.

SR-B81365 · Issue 331996

Enhanced security for IAC gadget

Resolved in Pega Version 7.4

The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.

SR-D32528 · Issue 502218

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.4

When using Microsoft Internet Explorer, checkboxes were slow to respond. For example, when clicking two checkboxes in succession, the second checkbox did not change. This was traced to the Layout Resize function getting called numerous times by the _toDisableSlideOnTabsClick and _resizeActions functions during onload refresh. This has been resolved by updating the system so that an LG header cell item checkbox click will not trigger the resize.

INC-164620 · Issue 640661

jQuery variable handling updated for mashup

Resolved in Pega Version 8.6.1

After update, embedded mashup was not working. The browser console log showed the error "Uncaught TypeError: $ is not a function at pega.web.manager._initGadgets (PegaReg?pyActivity=pzIncludeMashupScripts:69)". The $ function belongs to the jQuery library, and investigation traced this to a difference in variable handling. This has been corrected by updating the referring jQuery to use the variable 'jQuery' instead of '$'.

SR-D32528 · Issue 502217

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.2.5

When using Microsoft Internet Explorer, checkboxes were slow to respond. For example, when clicking two checkboxes in succession, the second checkbox did not change. This was traced to the Layout Resize function getting called numerous times by the _toDisableSlideOnTabsClick and _resizeActions functions during onload refresh. This has been resolved by updating the system so that an LG header cell item checkbox click will not trigger the resize.

SR-D32528 · Issue 502216

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.3.2

When using Microsoft Internet Explorer, checkboxes were slow to respond. For example, when clicking two checkboxes in succession, the second checkbox did not change. This was traced to the Layout Resize function getting called numerous times by the _toDisableSlideOnTabsClick and _resizeActions functions during onload refresh. This has been resolved by updating the system so that an LG header cell item checkbox click will not trigger the resize.

INC-164620 · Issue 640658

jQuery variable handling updated for mashup

Resolved in Pega Version 8.5.6

After upgrade, embedded mashup was not working. The browser console log showed the error "Uncaught TypeError: $ is not a function at pega.web.manager._initGadgets (PegaReg?pyActivity=pzIncludeMashupScripts:69)". The $ function belongs to the jQuery library, and investigation traced this to a difference in variable handling. This has been corrected by updating the referring jQuery to use the variable 'jQuery' instead of '$'.

SR-D92734 · Issue 553412

Simulation can take Data flow type as destination

Resolved in Pega Version 8.1.9

Support has been added for Data flow functionality as simulation target and data transform in simulation input.

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