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-133040 · Issue 202460

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-133241 · Issue 203013

Enabled NotFutureDate date for Thai Locale

Resolved in Pega Version 7.1.9

The validation notfuturedate was failing with the current date when using the Thai locale. The getDateFromFormat function has been updated to properly localize.

SR-133352 · Issue 206143

Calling Page-Set-Messages via activity now properly displays errors

Resolved in Pega Version 7.1.9

After upgrade, calling Page-Set-Messages via an activity did not appear to set messages on the harness. Changing the id ErrorTable to ErrorTable1 in the Errors section displayed the messages, but without any formatting or expand/collapse section. The error messages were indeed being set properly, but were being reset due to a rollback request to pzUpdateElementModel. To resolve this, pzKeepPageMessages is now being sent as true for rollBackElementUpdate request in pzpega_ui_doc_lifecycle.js to retain the errors displayed after the request.

SR-133352 · Issue 206222

Calling Page-Set-Messages via activity now properly displays errors

Resolved in Pega Version 7.1.9

After upgrade, calling Page-Set-Messages via an activity did not appear to set messages on the harness. Changing the id ErrorTable to ErrorTable1 in the Errors section displayed the messages, but without any formatting or expand/collapse section. The error messages were indeed being set properly, but were being reset due to a rollback request to pzUpdateElementModel. To resolve this, pzKeepPageMessages is now being sent as true for rollBackElementUpdate request in pzpega_ui_doc_lifecycle.js to retain the errors displayed after the request.

SR-133388 · Issue 203251

Fixed space overrun display issues for localized text in Designer Studio

Resolved in Pega Version 7.1.9

If the localized non-English text length was lengthy, it was overrunning its space and crossing into adjacent sections of the Explorer tab of Designer Studio. This has been corrected by adding style code to handle the left and right orientation of tabs, which is especially critical for Japanese and Arabian characters.

SR-133501 · Issue 202754

Error icons and localization corrected for repeating tabs headers

Resolved in Pega Version 7.1.9

The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.

SR-133545 · Issue 205543

Removed cleartext password in Operator password change URL

Resolved in Pega Version 7.1.9

The Change Password dialog in the Operator Full Profile provided cleartext of passwords as parameters in URL. The form method has been changed to POST in the HTML for the operator password reset popup to resolve this.

SR-133549 · Issue 203775

Added localization for "next" in new work item tab

Resolved in Pega Version 7.1.9

In the Case Manager portal, the 'next' label of a newly opened work item tab was not being localized. That has been fixed.

SR-133556 · Issue 206065

Corrected dropdown value reset following OnChange

Resolved in Pega Version 7.1.9

When a Clipboard page populated through an activity that retrieves data from an external table was used as a source for a drop-down, any validation errors would cause a return to the same screen but the selected value was not retained in the drop-down even though it appeared to be present on the clipboard. This was an issue with the drop-down option having leading/trailing spaces, and has been corrected.

SR-133611 · Issue 205327

Newline conversion added to enable search Autocomplete

Resolved in Pega Version 7.1.9

Despite results being present on the clipboard, Autocomplete was not displaying matching results during a search. This issue was due to newline characters present in the response JSON causing exceptions while calling eval() on the response string. To fix the issue, new line characters will be converted to
before parsing the results.

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