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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A642 · Issue 206621

Enabled section autogeneration from HTML to JSP

Resolved in Pega Version 7.1.9

Effective with Pega7, section generation was changed from HTML(pyJavaGenerateAPIVersion = 04-01) to JSP(pyJavaGenerateAPIVersion = 04-02). This caused an issue with some migrations from earlier versions that were not able to make the mandatory switch from HTML to JSP generation due to a missing option in the section ruleform. The option to upgrade from HTML to JSP had been configured from within "pyAutoHTML = false", meaning that this option appeared only for non-autogenerated sections. To resolve this, the option "Generate for" in the section Rule-HTML-Section.pzRuleFormHTML is now available irrespective of whether pyAutoHTML is set to true or false.

SR-A681 · Issue 205448

Added handling for empty section name in reload

Resolved in Pega Version 7.1.9

A Null message was sporadically displayed when hovering over a row instead displaying the SmartInfo section or a loading icon. This was caused by an empty section name in the reload section ajax, and handing for this has been added to the SmartHarness API.

SR-A833 · Issue 204781

Fixed Google Chrome 43 population of Dynamic Select and Menu control

Resolved in Pega Version 7.1.9

When using Google Chrome Version 43.0.2357.81 m, no values were shown in the Dynamic Select drop down list or in the Menu control. This was due to an uncaught exception for this browser in the JavaScript code which has now been addressed.

SR-A91 · Issue 205459

Added expand on click logic to check for layouts collapsed on open

Resolved in Pega Version 7.1.9

The ?Expand/Collapse? click event was not working on the first click if all layouts/sections were initially collapsed on open. This was due to the logic used to determine the state of the layouts, and an additional check has been inserted to handle scenarios where the layouts/sections are collapsed on-load.

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