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-A101069 · Issue 270616

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 269981

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101069 · Issue 270595

Fixed dropdown issues when using Google Chrome

Resolved in Pega Version 7.2.2

The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.

SR-A101027 · Issue 270450

Spellchecker call respects false setting

Resolved in Pega Version 7.2.2

The includeHeaderIcon method included spell checker scripts when the bIncludeSpellChecker parameter value was not equal to true. This has been fixed.

SR-A99523 · Issue 266451

LockInformation section uses field value label

Resolved in Pega Version 7.2.2

The label in pzLockInformation section was hard coded, causing the string "You have lost the lock! Please reopen the item to continue your work." to not have a field value. This has been changed to create a Field Value and use the same in the label.

SR-A21996 · Issue 249430

Timing logic updated for better BusyIndicator hide

Resolved in Pega Version 7.2.2

The logic for the performInsertCallback, loadAppendedRow, afterLoadRow, and editRowCallback functions has been improved to prevent a race condition that sometimes caused the busy indicator to not be correctly hidden on complicated repeat grids with many actions built on CPM.

SR-A86473 · Issue 255275

GeneralFailDetails section updated to resolve character error

Resolved in Pega Version 7.2.2

The non-auto GeneralFailDetails section has been updated to fix an issue where the decodeCrossOSString java API was causing an 'unexpected character' error.

SR-A100367 · Issue 270660

Page copy works when previewing a rule

Resolved in Pega Version 7.2.2

The option to copy an existing page was not working when previewing a rule. This was caused by the page type and page name parameters not being included in the pyTempWorkPage used to create the request URL for the preview; this has been corrected.

SR-A70596 · Issue 259237

Property validation message does not include property ID and rule name

Resolved in Pega Version 7.2.2

The property ID and rule names were being displayed in inline error messages due to them not being generally localized. This has been resolved by adding Field values to replace the static string used to show error messages for all the components and updating the error message generation in all the functions.

SR-B2949 · Issue 272615

Property validation message does not include property ID and rule name

Resolved in Pega Version 7.2.2

The property ID and rule names were being displayed in inline error messages due to them not being generally localized. This has been resolved by adding Field values to replace the static string used to show error messages for all the components and updating the error message generation in all the functions.

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