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.

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.

SR-B2863 · Issue 275455

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

SR-B2863 · Issue 275455

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

SR-B34026 · Issue 292199

Added check for offline case to avoid unsupported refresh

Resolved in Pega Version 7.3

Refresh other section is not supported in offline case, but was generating a Null Pointer Exception in the logs. This has been fixed by adding a check that will not generate the java code for Data transform for refresh other section in an offline case.

SR-B34274 · Issue 291209

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

SR-B35863 · Issue 294534

Mobile visibility condition fixed

Resolved in Pega Version 7.3

A section with visibility condition expressions on two properties was not displayed on mobile when the conditions were satisfied. The root cause for the issue was two change trackers being created for the same thread, which caused an override of the tracker properties. To solve this, the isSingleTracker API in change tracker has been modified to count the number of trackers instead of using a stored variable.

SR-B36175 · Issue 293408

Signature controls fixed for offline cases

Resolved in Pega Version 7.3

Signature capture controls were not capturing the signature on mobile devices. This was caused by Signature control being incorrectly disabled based on workobjID for offline cases, and has been fixed.

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