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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B39293 · Issue 299867

Mobile checkbox controls fire validations

Resolved in Pega Version 7.3

Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.

SR-B40310 · Issue 299601

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B6158 · Issue 275668

Updated mobile attachment error handling

Resolved in Pega Version 7.3

Incorrect behavior was seen on mobile when limiting file types using a trigger / when rule. The file type was ultimately evaluated and not attached, but the 'File attached Successfully' message was displayed on the mobile device. This has been fixed with an added check to evaluate whether the attachment is one of the accepted types, and the error markup has been updated.

SR-B6500 · Issue 276002

Mobile performance improvements for static content load

Resolved in Pega Version 7.3

Performance improvements have been made for mobile by enabling concurrent parallel load of static content.

SR-B7965 · Issue 291732

Resolved mobile case switching exception

Resolved in Pega Version 7.3

The console error 'Exception while trying to set work item as completed in assignment list' was seen while context switching a case in a custom mobile app. This was caused by the configuration calling submit during preprocessing, and has been fixed by ensuring the onSuccess callback of finishAssignmentAction is called when there is no next Task.

SR-B9286 · Issue 278610

Enhancement to get work items from multiple workpools for mobile user

Resolved in Pega Version 7.3

An enhancement has been added to support multiple workpools belonging to same application for mobile users. The code will iterate through all workpools which are offline enabled for the operator and get the work items in pzDataSyncGetWorkList activity.

SR-B9286 · Issue 287888

Enhancement to get work items from multiple workpools for mobile user

Resolved in Pega Version 7.3

An enhancement has been added to support multiple workpools belonging to same application for mobile users. The code will iterate through all workpools which are offline enabled for the operator and get the work items in pzDataSyncGetWorkList activity.

SR-B9718 · Issue 286254

Corrected picking for mobile circumstanced harness

Resolved in Pega Version 7.3

On mobile devices the circumstanced version of tablet was getting picked instead of the mobile device. The invoke addSectionForOfflinePackaging_X method has been updated to resolve this.

INC-153805 · Issue 627966

Mobile app language remains consistent after data sync

Resolved in Pega Version 8.4.5

When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.

INC-155640 · Issue 622977

Mobile logging updated for data page required parameters

Resolved in Pega Version 8.4.5

After upgrade, the number of warnings increased substantially in the mobile app log file for D_Pages, specifying "Required parameter X for data page X cannot be blank." This was traced to the forced logging related to missing required parameters for Parameterized DataPages during DeltaSyncs. In order to increase the value of the logging, the process has been moved from being called before packaging the Data Page to being printed later in packaging code and set to warn only about any unsupported data page configuration with required parameters.

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