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-D50584 · Issue 518442

Security added to retrieving operator list by URL extension

Resolved in Pega Version 8.2.6

It was possible to append information to the application URL which allowed an unauthenticated user to find a list of operators. This has been corrected, and will now result in the message "There has been an issue; please consult your system administrator."

SR-D56148 · Issue 537404

Corrected map zoom issue with iOS13

Resolved in Pega Version 8.2.6

After including a map control with markers in an application for iOS13, viewing via a mobile app and zooming introduces a gray bar across the map. This has been resolved by setting transform translateZ to the div of address map.

SR-D68810 · Issue 532133

Google street view enabled

Resolved in Pega Version 8.2.6

The Google Maps street view control has been enabled by setting streetViewControl to true in pzpega_ui_addressmap .

SR-D70674 · Issue 535483

Handling added for mobile upload of filename containing dots

Resolved in Pega Version 8.2.6

An issue with uploading a file name containing dots (such as 2019.12.12) while using the mobile browser has been resolved by updating the AttachFile activity in the propertyExist function.

SR-D73237 · Issue 539125

Pagination updated to resolve repeating Pulse notes

Resolved in Pega Version 8.2.6

After adding a case and entering 15 Pulse notes, scrolling down resulted in the notes being duplicated. Investigation traced this to entering more than 10 posts in a single interaction on a previously empty case when "Progressive pagination" was enabled for the repeating dynamic layout. On Private Edit, if the pagination was changed to "NONE" then the issue was resolved. Pagination depends on the pzPagingStartDateTime property, which is set on D_pzFeedParams, but since there were no results in this scenario this property was not being set. To resolve this, an update has been made so that pzPagingStartDateTime will be set if it is empty.

SR-D74246 · Issue 543725

Accessibility improved for Pega Survey Question pages

Resolved in Pega Version 8.2.6

Question Pages in Pega Survey lacked accessibility. This was traced to aria-label not being generated for Radio buttons and Drop-downs, and "title" not being generated for other controls used in Question and Question Pages. This has been resolved.

SR-D76927 · Issue 541422

VirusCheck added to all Pulse uploads

Resolved in Pega Version 8.2.6

The upload file activity has been updated to invoke VirusCheckActivity for all Pulse uploads.

SR-D50787 · Issue 520484

Excel time values will default to server datetime if operator time zone is null

Resolved in Pega Version 8.2.6

After upgrade, a scheduled report that contained a column using pxDateTime that was supposed to use EST instead used GMT when run and exported to Excel. This has been resolved with an update that will default to using the time zone of the server If the time zone of the operator is empty or null.

SR-D50819 · Issue 519237

Eligibility Builder integer sorting revised

Resolved in Pega Version 8.2.6

In 'Offer' on the Eligibility tab, the Builder was sorting integer properties by the value of the integer as a text string rather than the whole number. Example: 1, 10, 12, 13, 100, 2, 20, 29, 299, 3 instead of the expected 1, 2, 3, 10, 11, 12, 20, etc. This was traced to the system sorting the results using tools.sortPageList() in order to sort by localized (string) value, which is not appropriate for values of any type other than string. To resolve this, the system will skip the manual sort step for numeric columns since the values are appropriately sorted by the database.

SR-D53176 · Issue 541794

Error when adding function filter will persist

Resolved in Pega Version 8.2.6

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

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