SR-D85624 · Issue 552695
Corrected browser displaying checkboxes as sliders
Resolved in Pega Version 8.2.7
Checkboxes were displaying as sliders in Microsooft internet Explorer version11.1304.17134.0 due to the browser returning Table pc 2.0. Since Pega HTML class includes tablet, .tablet related styles were getting picked up and displaying the checkboxes in tablet mode. To resolve this, a check has been added to pyIsTablet to evaluate correctly at runtime.
SR-D90279 · Issue 554390
Data sync updated for use with DeferWrite
Resolved in Pega Version 8.2.7
After update, attempting a data sync from the client mobile application worked for the first object submission, but the second object failed and stayed in the list. This was traced to finish assignments running back to back when deferWrite was enabled and svcPerformFlow failed to find the assignment. To resolve this, the assignmentHandle will be passed to the activity when calling the pzSetDeferWrite activity from FinishAssignmentActionProcessor.
SR-D91532 · Issue 556404
Resolved Clear Cache error for mobile client
Resolved in Pega Version 8.2.7
When attempting to clear local storage while logged into the Mobile Client, the error message "You need to be able to connect to the server in order to clear the storage" appeared. This was traced to the application being configured to disable a user's web session immediately after log in, and was due to the "Clear Cache" functionality failing while attempting an AJAX request to invoke the server's "pzAmIOnline" activity. While there was a workaround of using the check box "Access group requires a connection for portions of the application", this has been resolved by updating the Settings - Clear Cache functionality in order be able to detect if it's online in a different way.
SR-D28965 · Issue 501859
Repository document deletion modified for better cleanup
Resolved in Pega Version 8.1.7
When using documents functionality, creating and uploading a document properly stored it, but deleting the document did not remove the associated files from storage. Whenever a document is created that has a file, instances Of Link-Attachment and Data-WorkAttach-File are also created. Previously, when the document was deleted, the associated instances and actual file were not deleted from the repositories but rather marked as Resolved-Withdrawn and hidden at the UI level. The system has now been updated so that when a document is deleted, the document attachment will also be deleted from all places like list, Tile, and document View, and reference instances like Link-Attachment and Data-WorkAttach-File instance will also be removed along with the actual file from the repository.
INC-182423 · Issue 691798
Pull to refresh disabled during case submission
Resolved in Pega Version 8.5.6
Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.
INC-187230 · Issue 672472
Resolved exception during LDP processing
Resolved in Pega Version 8.5.6
A ConcurrentModificationException was appearing during the processing of Large Data Pages. This has been resolved with the addition of a lock on clear method in ConcurrentReplicatedPage.
INC-194932 · Issue 689290
Handling updated for offlineWorkIDs map
Resolved in Pega Version 8.5.6
Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.
INC-195519 · Issue 698496
Support added for using CFW when Pega server is unavailable
Resolved in Pega Version 8.5.6
Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.
INC-195601 · Issue 685769
Basereference context available for attach content control
Resolved in Pega Version 8.5.6
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-206049 · Issue 703470
Resolved activity registration error for Scan Barcode/QR Code
Resolved in Pega Version 8.5.6
Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.