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-123581 · Issue 188015

Scrolling corrected for Safari on mobile devices

Resolved in Pega Version 7.1.8

When using the global search on a tablet or mobile device, the results are displayed in a modal pop up in the browser. However, scrolling was not working when using Safari on a mobile device. To correct this, the Search Panel CSS and js were modified to enable scroll support on mobile devices.

SR-125913 · Issue 192447

Fixed file attachments in Mobile

Resolved in Pega Version 7.1.8

When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.

SR-A18905 · Issue 233955

OrgName error resolved for MobileOffline:Obj-Open-By-Handle

Resolved in Pega Version 7.2.1

If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.

SR-A21298 · Issue 239141

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

SR-A21636 · Issue 240162

Fixed auto-complete use in iPhone Opportunity creation

Resolved in Pega Version 7.2.1

Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.

SR-A24787 · Issue 247535

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

SR-A24787 · Issue 245849

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

INC-157214 · Issue 634986

Mentioned user in Pulse appears correctly

Resolved in Pega Version 8.6.1

When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.

INC-160485 · Issue 655298

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.6.1

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-161398 · Issue 639853

DataSync SynchronizationResponseStreamer logging enhancements

Resolved in Pega Version 8.6.1

The PegaRULES log contained "Response page does not match request, will generate failure response" errors even though no functional impact was observed. In order to enhance troubleshooting, additional DEBUG logs have been to DataSyncHandler, SynchronizationResponseStreamer is now logged on INFO level and contains more detail, and the error message has been modified to "Cannot prepare continuation response because offline package was stale. Will generate reset schedule response." to be more informative.

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