INC-151998 · Issue 616321
Offline mobile RDL attach updated
Resolved in Pega Version 8.6
It was not possible to attach any file using the attach content control while the mobile app was configured as offline and property reference was used for the file name in the attachment control. No issues were seen if a static file name was used. This has been resolved by updating the RDL Attach content handling.
INC-152217 · Issue 613929
Activity updated for Mobile attachment access
Resolved in Pega Version 8.6
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-153133 · Issue 612726
Updated encryption and decryption handling for non-auto control
Resolved in Pega Version 8.6
After encrypting the pyMessage from PegaSocial-Message, the message was displayed in Pulse in the encrypted form. This was caused by a difference in handling between auto and non-auto controls, where the decryption was only handled automatically in the auto controls. To resolve this, explicit encryption and decryption handling has been added to the non-auto control.
INC-153423 · Issue 615665
Timing update for Signature Capture Control
Resolved in Pega Version 8.6
A signature could be lost when using the signature capture control if a signature was drawn then the Accept and Submit links were clicked in quick succession. The problem occurred more frequently (although was not limited to) when there were multiple signature capture controls on the screen. This issue was due to transaction mismatch error for few pzAttachSignatureWrapper requests (signature post requests) caused by triggering the next accept request before completing the previous accept request. To resolve this, an update has been made to display busy indicator immediately when the first accept button is clicked.
INC-153805 · Issue 627968
Mobile app language remains consistent after data sync
Resolved in Pega Version 8.6
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-154290 · Issue 613472
Signature capture exception resolved
Resolved in Pega Version 8.6
The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.
INC-155214 · Issue 617005
GetBinaryFilesRef updated for resolving wildcard
Resolved in Pega Version 8.6
After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.
INC-155640 · Issue 622979
Mobile logging updated for data page required parameters
Resolved in Pega Version 8.6
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. As a workaround, the warnings may also be added to a denylist in "Dev Studio > Configure > Mobile > Offline Configuration" to block them.
INC-155752 · Issue 622773
Hidden Question pages and answers will be saved to DB
Resolved in Pega Version 8.6
After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.
INC-156211 · Issue 620194
Verbose comments removed from wrapper
Resolved in Pega Version 8.6
Comments with references to external links have been removed from some harness wrappers.