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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to 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.

INC-152542 · Issue 610947

Support extended for document tags

Resolved in Pega Version 8.7

An enhancement has been added to extend the support for document tags, including showing tags added to a case in a workpool other than the application workpool; showing tags from other operators such as partner sales rep, sales reps, etc; and displaying tags in the "recently added by me" section.

INC-160485 · Issue 655297

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.7

Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.

INC-161214 · Issue 640893

Push notification of shape-created child case opens correct case

Resolved in Pega Version 8.7

In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.

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