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-126885 · Issue 193150

Check added to avoid multiple submits from custom controls with refresh

Resolved in Pega Version 7.2

After upgrading, double-clicking on a custom control button with a refresh harness caused a form to be submitted multiple times and an exception was generated. A check has been added to avoid multiple submits of the same form.

SR-A12648 · Issue 225025

Localization restored for pyCaption (backwards compatibility)

Resolved in Pega Version 7.2

After upgrade, the sub case of a work object was not being translated using pyCaption field value. Using pyLabel field value worked as expected. This was a backward compatibility issue, and localizing on pyCaption or property value has been restored for use.

SR-A12357 · Issue 225139

Improvement made to UI error message persistence

Resolved in Pega Version 7.2

Error messages were being cleared from the UI even when they were present on the clipboard. This made it difficult to isolate the error in data entry screens with many fields, leading to confusion and multiple submits to regain the error messages. This has been resolved by updating the loadtabcontents method to pass the pzKeepPageMessages parameter.

SR-A13963 · Issue 227442

Dropdown control updated for Apple mobile Safari

Resolved in Pega Version 7.2

The Apple mobile Safari webview displayed a problem with updating the state of selection in a dropdown, creating scenarios where two values were shown as selected or previously selected values were lost. This was traced to the DOM selector "option:selected" selecting multiple options by accumulating all of the selections done by the user up to that point in time. The databinder function has been modified to handle this specific environment for dropdowns.

SR-A12915 · Issue 225381

Error messages remain visible with GetTargets

Resolved in Pega Version 7.2

If there were error messages (page-set-messages or property-set-messages) and the GetTargets activity was called on the page, the error messages disappeared. This was traced to the pzKeepPageMessages's request header value being false, and the "callGetTargets" method has been updated to pass pzKeepPageMessages parameter.

SR-A13446 · Issue 225382

Consistent width for GenerateDatePicker validation messages

Resolved in Pega Version 7.2

Due to a problem with the inclusion of the GenerateDatePicker error message div in the control's span markup, any validation message had inconsistent widths. This has been fixed.

SR-A8538 · Issue 222591

RepeatIndex generation improved

Resolved in Pega Version 8.1

Controls in a triple layout included in a row repeat did not have matching unique IDs and label for attributes. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.

SR-A11550 · Issue 222998

State abbreviations will not be localized

Resolved in Pega Version 7.2

A dropdown sourced from a datapage that contains region abbreviations was incorrectly localizing the US state abbreviations for entries such as Indiana ("IN") to be lowercase ("in"). By default the dropdown options are localized, but a check has been added to bypass default localization if the source is a Field Value.

SR-A11170 · Issue 222267

State abbreviations will not be localized

Resolved in Pega Version 7.2

A dropdown sourced from a datapage that contains region abbreviations was incorrectly localizing the US state abbreviations for entries such as Indiana ("IN") to be lowercase ("in"). By default the dropdown options are localized, but a check has been added to bypass default localization if the source is a Field Value.

SR-A5880 · Issue 216627

Updated error label highlighting for reused sections

Resolved in Pega Version 7.2

The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.

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