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-A1604 · Issue 206062

Other Actions submit API updated

Resolved in Pega Version 7.1.9

When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.

SR-A1616 · Issue 205609

Fixed section refresh issue in Google Chrome

Resolved in Pega Version 7.1.9

When using the Google Chrome browser, a section that was included inside a repeating dynamic layout and configured to refresh based on the value of a radio button control which itself was included in another section and configured to post its value on change was refreshed as expected in dev portal but not in IAC. This was due to changes in the value list not populating properly in Google Chrome on IA, and the logic for parsing change tracker div has been modified to correct this.

SR-A1647 · Issue 205606

Removed duplicate special character encoding on FieldValue validation

Resolved in Pega Version 7.1.9

A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.

SR-A168 · Issue 203378

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-A1732 · Issue 206294

Corrected mixed character autocomplete for JSON data

Resolved in Pega Version 7.1.9

Autocomplete was not populating values If a field used a mix of alphanumeric and special characters. This was an issue caused by exceptions generated when the field "PlantName" contained new line characters in the response JSON. To fix the issue, new line characters are converted as
before parsing the results.

SR-A1732 · Issue 206388

Corrected mixed character autocomplete for JSON data

Resolved in Pega Version 7.1.9

Autocomplete was not populating values If a field used a mix of alphanumeric and special characters. This was an issue caused by exceptions generated when the field "PlantName" contained new line characters in the response JSON. To fix the issue, new line characters are converted as
before parsing the results.

SR-A1848 · Issue 206991

Added handling to retain checkbox value on harness reload

Resolved in Pega Version 7.1.9

Clicking on 'Save Draft' was causing a checkbox in the work object screen which was checked (i.e. value is true) and disabled to have its value removed. This was traced to logic for disabled checkboxes that did not submit the corresponding hidden value if the reload harness ajax was missing. Checkbox value handling has been added to the form submit to resolve this.

SR-A1852 · Issue 209275

Resolved error on tab switching in DS portal

Resolved in Pega Version 7.1.9

After logging into Pega Designer Studio and launching a portal, performing a switch role/portal in the opened portal and then clicking on the Designer Studio tab closed the secondary portal tab. This was resolved, but an additional problem arose with an error being generated for the tab that was opened previously before switching applications when trying to save or modify the availability of already opened rules in the dev portal. This had to do with the API used to clean up the threads, and has been corrected.

SR-A1959 · Issue 209485

Corrected checkbox behavior with freeze header

Resolved in Pega Version 7.1.9

In repeat grids where freeze header was checked throughout the application and data was populated by page list, running the flow on selecting a check box for a single row resulted in all the check-boxes of the grid getting selected. This was an issue where the API "checkAllIfInHeader" incorrectly assumed that the checkbox was in the header for each row, which caused all the checkboxes of the row to change according to the checkbox that had been changed. To prevent this, a condition has been added to "checkAllIfInHeader" to exit if it is inside a row and not in the header.

SR-A2009 · Issue 206469

Fixed inconsistent tab 'visible when' behavior

Resolved in Pega Version 7.1.9

In a section with a tabbed repeat using 'body visible when', invoking a list which changed the when condition so that the tab becomes visible in the tabbed repeat created various issues after checking the visibility including invisible data, empty tabs, and duplicate tabs. This was traced to the placement of visible when conditions in the RUF causing the DIVs to be closed incorrectly, and has been fixed.

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