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-D53266 · Issue 516395

Synchronization continuation updated so mobile attachments properly preview

Resolved in Pega Version 8.3.2

Clicking on attachments in mobile would open them if the attachment had just happened, but otherwise would not open them at all. This was traced to an issue with Synchronization continuation: the page was properly loaded from database but its content was not used to fill the named OfflinePackage page (which contains only the search keys). This has been corrected by replacing the empty page with the one loaded from the database.

SR-D55559 · Issue 520972

Setting added to allow commas in bulk upload survey questions

Resolved in Pega Version 8.3.2

Questions uploaded in bulk to Survey Designer were delimited by comma, potentially causing an issue when an option itself contains a comma. Because this is a hard-coded Excel template value, this has been addressed with the addition of an extension where delimiter values can be configured and overridden.

SR-D67150 · Issue 532022

Resolved attachments when using Mobile page message setting

Resolved in Pega Version 8.3.2

When using page-level error messages for a work object, trying to add an attachment to that work object resulted in an error and the attachment failed. This has been resolved by adding an error check in the pzAttachContentFile activity.

SR-D74839 · Issue 537321

Corrected map zoom issue with iOS13

Resolved in Pega Version 8.3.2

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-D76927 · Issue 541421

VirusCheck added to all Pulse uploads

Resolved in Pega Version 8.3.2

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

SR-D81859 · Issue 543764

Maps and signatures inside layout groups scroll correctly

Resolved in Pega Version 8.3.2

A map configured in the screen was getting grayed out while scrolling horizontally. Analysis showed that when an address map is inside a layout group, the layout group swipe was triggered instead of scrolling. To resolve this, the target parent now has the data attribute "data-nogestures" = true so the layout group swipe will not be triggered. This will also prevent swipe on signature while scrolling horizontally.

INC-160485 · Issue 655296

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.5.5

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-167139 · Issue 658620

Functions are packaged with "--" suffix

Resolved in Pega Version 8.5.5

Validation rules were not executed as expected. Investigation showed this was caused by functions referenced in the validate rule through a function alias being packaged without the "--" suffix (for example isNameInvalid--(String) was packaged as isNameInvalid). This has been corrected.

INC-168290 · Issue 663426

Signature Accept callback fires correctly in offline app

Resolved in Pega Version 8.5.5

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-172124 · Issue 651291

Improved Operator ID selection in Mobile Logs Retrieval section

Resolved in Pega Version 8.5.5

Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.

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