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-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.

SR-B88728 · Issue 337054

Currency control check added for iOS

Resolved in Pega Version 7.4

Currency control with 'readonlyformat' enabled was generating markup such as

SR-B89375 · Issue 339299

Activity added to access showDesktop parameters

Resolved in Pega Version 7.4

In mobile, after launching the portal to see a list of assessments assigned to a particular patient ID and then leaving that screen static for 30 minutes or more, reactivating the session and logging in to the parent page with another patient ID re-displayed the previous patient's data. This was due to a successful log off not being triggered combined with the lack of a hook in the showDesktop activity flow to get the new parameters. To fix this, a new available activity "pyrequestorSetupExtension" has been added to access parameters passed to showDesktop activity.

SR-B92957 · Issue 340583

Address map loads correctly on mobile app

Resolved in Pega Version 7.4

The address map was not loading on a mobile device even if the device was connected to a network. This was due to the App ID not being included in the script properly during generation due to recent templating changes, and has been fixed.

SR-B95564 · Issue 346568

Mobile Pulse issues corrected

Resolved in Pega Version 7.4

Issues with posting Pulse messages in Pega Mobile express have been fixed, and Pulse subtabs are now displayed for all WOs.

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