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

SR-B36260 · Issue 296921

Fixed mobile native control submit clearing property/date

Resolved in Pega Version 7.3

When the "native control on mobile" option is checked for a date-time property, a runtime error on submit cleared the property value/date value. To correct this, if the datetime property gets any error messages on submitting the screen, the response of the datetime control will not generate the Value or overwrite it.

SR-B38958 · Issue 296022

Updates to field values reflected on mobile

Resolved in Pega Version 7.3

After updating field values in higher ruleset versions and forcing a full data sync, the mobile app did not reflect the updated value. This was due to rule resolution not happening while packaging the FieldValue rules due to locale, and has been corrected by changing the PZGETFIELDVALUES rule to sort the pzInsName based on the ruleset versions and picking the latest available rules from the ruleset.

SR-B39293 · Issue 296727

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-B39293 · Issue 297091

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

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