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-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-A7290 · Issue 216208

Made autocomplete field visible for mobile

Resolved in Pega Version 7.2

There was a problem with the visibility of the autocomplete field when used for add/remove buttons on mobile. The webkit-transform function was updated for smoother transition.

SR-A2677 · Issue 213336

Updated autocomplete to accept shift-key characters

Resolved in Pega Version 7.2

The autocomplete function was not correctly incorporating keystroke combinations that required the shift key, such as '_' when showing results. This has been fixed.

SR-A4648 · Issue 211547

Updated autocomplete to accept shift-key characters

Resolved in Pega Version 7.2

The autocomplete function was not correctly incorporating keystroke combinations that required the shift key, such as '_' when showing results. This has been fixed.

SR-A23339 · Issue 247921

Non-versioned class rule forms updated during upgrade

Resolved in Pega Version 7.2.1

The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.

SR-B37923 · Issue 295190

null-pointer exception fixed for ForceCaseClose

Resolved in Pega Version 7.3

An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.

SR-D27041 · Issue 499048

Manual value group addition support available

Resolved in Pega Version 8.4

In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.

INC-139130 · Issue 591861

Tab Headers accessible in Report Filter with keyboard

Resolved in Pega Version 8.6

Tab Headers such as "Available Values" were not accessible with a keyboard in the modal to select values for Report Filters. Instead, the focus marker directly shifted to content and toggling between Tabs was not possible. Investigation showed that at runtime for report definitions, the value for prevElement was null, which threw an error and caused the rest of the function to not run. This has been corrected by adding null checks for prevElement and newElement in the function tabClickCallback in the pega_report_events js file.

SR-D27041 · Issue 499047

Manual value group addition support available

Resolved in Pega Version 8.1.6

In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.

SR-D27041 · Issue 499046

Manual value group addition support available

Resolved in Pega Version 8.2.3

In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.

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