INC-191412 · Issue 692674
Large Data page join condition available for Mobile
Resolved in Pega Version 8.6.5
Support for a join condition has been added to the Large Data page for use in Mobile to match the use available on desktop.
INC-198193 · Issue 723624
Error correctly shows for each attempt to upload an oversize file
Resolved in Pega Version 8.6.5
The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.
INC-205683 · Issue 702561
Data transform actions supported in offline app
Resolved in Pega Version 8.6.5
Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.
INC-222126 · Issue 721903
Improvement for mobile display error related to harness timing
Resolved in Pega Version 8.6.5
After updating from 8.1 to 8.6, working very quickly on mobile to create a case and refresh it resulted in a "Display error" screen that included the message "Failed to find instance @baseclase.pyCreate of type Rule-HTML-Harness". This was caused by the system not being initialized with the needed content and some target parameters therefore being evaluated as null. A preliminary fix for closeDocCallback when WebView is not loaded has been added which has significantly reduced the frequency of this issue. Additional work will be done towards a complete resolution in a future release.
SR-B15685 · Issue 317888
Mobile autocomplete dropdown selections fixed
Resolved in Pega Version 7.3.1
When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.
SR-B71308 · Issue 319409
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.
SR-B71308 · Issue 320806
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.
SR-B54666 · Issue 320294
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js
SR-B54666 · Issue 316346
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js
SR-B57614 · Issue 322754
PegaMobile honors prompt for password check
Resolved in Pega Version 7.3.1
The Pega Mobile App option to 'Always prompt for password on start' was not saving the selected choice. This was caused by a conflict with "Do not save property data" in the persistence section of the property advanced settings, and has been fixed.