Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

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.

SR-B13785 · Issue 284743

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.

SR-B13785 · Issue 278965

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.

SR-B15685 · Issue 292401

Flexibility enhancement for mobile dropdown displays

Resolved in Pega Version 7.3

As a part of an enhancement for mobile apps, a checkbox for "Allow scrolling for more results" has been introduced in the property panel of the Autocomplete. By default its value will be unchecked, implying the old behavior which limits the "Dropdown" options on autocomplete to 8 for backward compatibility. If the checkbox is used, it will honor the "Max results displayed" setting used for list based autocomplete. If the max results value is not specified, using the checkbox will cause the dropdown to show all the results.

SR-B15880 · Issue 289450

Enable/disable of "+" icon in mobile app fixed

Resolved in Pega Version 7.3

The enabling and disabling of the "+" icon was not happening in the Mobile Hybrid app even when disabling condition were met. This has been fixed.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us