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-A75927 · Issue 252170

OnChange event fires correctly for pyAddress

Resolved in Pega Version 7.2.2

Using a pyLocationFieldOptional section that included pyAddress to get the real time address associated with the map would correctly update the address when the map marker was moved, but the OnChange event associated with the text box did not fire. This was due to the change event waiting until focus & blur events are dispatched on the referenced text input field. To correct this, the touch devices check in setAddressProperty function in pzpega_addressmap.js has been removed so that focus is fired and blurred after the change event is triggered. In addressmap js , the setAddressProperty function will dispatch change after focus & later will dispatch blur.

INC-137100 · Issue 604059

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.2.8

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-137100 · Issue 605837

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.3.5

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-137100 · Issue 604057

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.5.2

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-137100 · Issue 604060

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.4.4

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

SR-C39158 · Issue 379163

Sorting works for calculated field grid column

Resolved in Pega Version 8.1

Sorting was not working on a column when a date calculation function was given as a grid column sourced with a report definition. This has been fixed by adding the proper sort field in the DOM and correcting the check of pyFieldName in the gridSortpaginate activity.

INC-137100 · Issue 604058

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.6

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

SR-D60206 · Issue 529325

Resolved null pointer on Reference Helper startup

Resolved in Pega Version 8.3.2

An issue with the system failing to start and generating a NullPointerException on RUFReferenceHelper.java has been resolved by modifying some Rule-Utility-Function code to better handle threads that are not completely initiaized yet but still running rules.

SR-D77157 · Issue 544471

DataSet preview will use date instead of datetime

Resolved in Pega Version 8.3.3

While using a DataSet preview functionality, the date appeared as reduced by one day. This has been resolved by parsing date as 'date' instead of 'datetime' to avoid issues with timezone interactions.

SR-D77157 · Issue 544473

DataSet preview will use date instead of datetime

Resolved in Pega Version 8.4.1

While using a DataSet preview functionality, the date appeared as reduced by one day. This has been resolved by parsing date as 'date' instead of 'datetime' to avoid issues with timezone interactions.

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