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-A3004 · Issue 208289

Added escape character check to retain Repeating Grid filter choices

Resolved in Pega Version 7.1.9

Filter values were not being retained when multiple values were selected in a repeating grid if the value contained an ampersand ("&"). This has been fixed by adding a call to the StringEscapeUtils.unescapeHtml API.

SR-A3063 · Issue 208349

Ensured 'ReadOnly' consistently propagates to child section

Resolved in Pega Version 7.1.9

The Edit Option 'ReadOnly' was inconsistent about propagating to a child when a control followed a section include. This occurred because the pzsectionBodyIncludeInCell RUF removes the "SectionReadOnly" param after it has included the section, causing a problem in any trailing controls of the parent section because the "isControlEditable" API was depending only on "SectionReadOnly" and the read-only when/expression. This has been fixed by updating the "isControlEditable" API to additionally call the "hasInputEnabled" API to check the edit mode of the control.

SR-A3274 · Issue 210284

Updated en_US locale spellcheck

Resolved in Pega Version 7.1.9

Spellchecking on RTE control was not detecting some wrongly spelled words in the en_US locale. This was a regression, and has been fixed.

SR-A3421 · Issue 207837

Corrected Refresh based on clipboard property changes

Resolved in Pega Version 7.1.9

Refreshing the Dynamic layout whenever a property in the clipboard changed was not working in one of the cases in base CPM: when passing "ProcessAction" activity as a pre-activity for any flow action, change tracker did not send the changed values from the newAssignPage. This has been resolved by adding a condition for "ProcessAction" on pre-activity.

SR-A3654 · Issue 209567

Corrected decimal control mapping for Lithuanian locale

Resolved in Pega Version 7.1.9

Decimal control mapped to a decimal property was not accepting valid decimal properties for a Lithuanian locale where a dot is a decimal separator and comma is a thousands separator, ex a valid decimal value of '123.456.789,00'. A check has been added to the API that will utilize the proper grouping separator for the "lt_LT" locale .

SR-A4314 · Issue 210533

Enhancements added to ensure visible 'when' after upgrade

Resolved in Pega Version 7.1.9

After migration using systems upgraded in place, all pre-existing Default controls no longer showed the "Required" option in the cell properties, and the validation no longer functioned correctly (the form submitted successfully with previously required fields empty). The root cause was that pyAutoHTML was not set in XML, so the Visibility condition expression evaluated to false. This has been resolved by adding a check for empty visible-when conditions and by inserting pzNonAutoHTML, a newly created when rule which checks for empty or false values of pyAutoHTML for required checkbox visibility.

SR-A528 · Issue 206623

Resolved date format change on declare expression trigger

Resolved in Pega Version 7.1.9

When there is a declare expression configured for a date property, the format was getting changed once the declare expression was triggered. This has been resolved.

SR-A619 · Issue 205442

Page Messages displayed on dropdown after render

Resolved in Pega Version 7.1.9

When submitting a flow action that contains a dropdown control and which is configured to load its values after the screen renders, Page Messages were not displayed when the flow action was re-displayed. This was caused by "pzKeepPageMessages" not being set to "true" while sending the ajax request to fetch drop down options (for render after screen/load on hover), and has been corrected.

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.

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