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.

INC-130727 · Issue 573340

Resolved mobile app java.lang.OutOfMemoryError

Resolved in Pega Version 8.5.1

After working with the mobile app for a period, logging in failed and the app crashed with java.lang.OutOfMemoryError exceptions. This was traced to each sync adding a new version of allow-list datapages to the client store which were not cleared, and has been resolved.

INC-135159 · Issue 580675

Logic updated for deepMergeObj API

Resolved in Pega Version 8.5.1

Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.

INC-131991 · Issue 583041

Logic updated for deepMergeObj API

Resolved in Pega Version 8.5.1

Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.

INC-137352 · Issue 583664

Mobile app improvements for poor connectivity conditions

Resolved in Pega Version 8.5.1

When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.

SR-A102729 · Issue 272707

Mobile modal display timing corrected

Resolved in Pega Version 7.3

When the full screen for mobile device option was used while launching a local action, the template buttons (Submit and Cancel) appeared to be missing until the screen adjusted during a focus shift to an editable field. This was an issue with asynchronous display timing in the modal dialog template using dynamic layouts with client side visible whens, and has been fixed.

SR-B10667 · Issue 283291

IOS HC app login updated to better handle sync conflicts

Resolved in Pega Version 7.3

Intermittent HC iOS login failures or app crashes were accompanied by the error 'Client Store synchronization failed.' To resolve this, web-login has been updated to handle cases where login failure occurs while a sync is in progress.

SR-B12207 · Issue 285722

Corrected Org text field handling for templated mobile sections

Resolved in Pega Version 7.3

Given a section pyWorkSummary_Mobile with a text input field called Organization, the organization name was shown correctly in the Declare_crmOrg page but on the UI it was displaying 'Org Not Found'. This was caused by recent section template changes that caused the object to be rendered on the wrong thread, and has been fixed.

SR-B13431 · Issue 283632

Mobile App description localized in PegaExpress

Resolved in Pega Version 7.3

The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.

SR-B13431 · Issue 283681

Mobile App description localized in PegaExpress

Resolved in Pega Version 7.3

The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.

SR-B13785 · Issue 284733

Added tenant ID check for batch thread in MT environment

Resolved in Pega Version 7.3

When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.

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