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-B78159 · Issue 338952

Mobile dashboard widget name value displays correctly

Resolved in Pega Version 7.4

A problem was seen where the dashboard widget name tag was not resolved on the first visit to the dashboard, but after navigating to the second screen on a mobile device and then returning to the dashboard, the correct value appeared. This was traced to a missing use case for a header using JSP format, and has been corrected.

SR-B78996 · Issue 330406

Proxy Support added for "Mobile App Build" Mechanism

Resolved in Pega Version 7.4

The Mobile Application 'Build' mechanism was not picking up on the JVM Proxy Settings (-Dhttps.proxyHost, -Dhtps.proxyPort, -Dhttps.proxySet). This has been added.

SR-B82481 · Issue 333250

added safecheck to sectionRefreshCallback

Resolved in Pega Version 7.4

When doing a refresh of a section in the PSI app, the Hybrid client in function sectionRefreshCallback in pzpega_ui_ajaxengine.js was causing a crash. This was due to a missing safe check which has now been added.

SR-B82678 · Issue 338616

Optimistic packaging updated to handle missing pxflows

Resolved in Pega Version 7.4

Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.

SR-B82678 · Issue 338451

Optimistic packaging updated to handle missing pxflow errors

Resolved in Pega Version 7.4

Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.

SR-B84336 · Issue 332037

onOnlineDetected use matches documentation

Resolved in Pega Version 7.4

iOS11 was failing the first login attempt. Documentation for the addListener method in pzPega_offline_datasync rule lists 'onOnlineDetected' as optional, but when the listener was added without onOnlineDetected the console.error occurred. This was originally a documentation error where the rule was incorrectly given as optional even though the event handlers always assumed onOnlineDetected was defined, but as there are reasons to support this use the system has been updated this so onOnlineDetected is truly optional now.

SR-B87422 · Issue 337249

Mobile sync fixed for case data

Resolved in Pega Version 7.4

When a case was updated, the Pega iOSMobile application failed to sync the case data and became stuck due to read-only Data Pages being included in the action data. To ensure the update can be saved properly, code has been added to mergeWorkAndForm which will remove data pages before returning the action data.

SR-B87422 · Issue 337228

Mobile sync fixed for case data

Resolved in Pega Version 7.4

When a case was updated, the Pega iOSMobile application failed to sync the case data and became stuck due to read-only Data Pages being included in the action data. To ensure the update can be saved properly, code has been added to mergeWorkAndForm which will remove data pages before returning the action data.

SR-B88639 · Issue 338274

Handling added for non-runtime LDP exception

Resolved in Pega Version 7.4

An app was crashing and failing sync because of an incorrect LDP configuration. In order to make synchronization fail gracefully in case of a parsing error, the Hybrid Client has been updated to handle and re-throw a non-runtime exception.

SR-B88639 · Issue 338414

Handling added for non-runtime LDP exception

Resolved in Pega Version 7.4

An app was crashing and failing sync because of an incorrect LDP configuration. In order to make synchronization fail gracefully in case of a parsing error, the Hybrid Client has been updated to handle and re-throw a non-runtime exception.

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