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