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-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-168290 · Issue 663427

Signature Accept callback fires correctly in offline app

Resolved in Pega Version 8.6.2

Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.

INC-171951 · Issue 667123

Signature Accept callback fires correctly in offline app

Resolved in Pega Version 8.6.2

Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.

INC-172315 · Issue 664628

Resolved intermittent attachment save error

Resolved in Pega Version 8.6.2

A Flow Action error was intermittently being displayed when saving attachments. This was traced to the activity pzUploadAttachmentToDocument-->Step 25 which uses the step page CallExtensionAct which can cause a page null exception if it is not initialized, and has been resolved by adding a Page-New step to initialize the page.

INC-179175 · Issue 664046

Mobile barcode scan sets value with correct context

Resolved in Pega Version 8.6.2

After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.

INC-181126 · Issue 663306

Signature Accept callback fires correctly in offline app

Resolved in Pega Version 8.6.2

Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.

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