INC-183559 · Issue 664812
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.5.5
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-183864 · Issue 666185
Updated RequestorInitialize to improve performance
Resolved in Pega Version 8.5.5
After updating, initial user logins were taking an excessive amount of time. This was traced to the standard rule "RequestorInitialize", and has been resolved by updating the implementation.
INC-169636 · Issue 659533
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.5.5
When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following:webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg
INC-134618 · Issue 582776
Corrected logic for deep pagelists on mobile
Resolved in Pega Version 8.5.1
After completing a workorder in the mobile app, the synchronization failed intermittently with the error "fail: pyWorkPage - Validation failed: Errors Detected. Finish Assignment action failed as pyWorkPage has messages: Validation failed: Errors Detected. ... The page contains an undefined property: .pxUniqueElementID". This was traced to incorrect logic for handling deep pagelists, and has been resolved.
INC-131961 · Issue 571700
Mobile app correctly determines online status after sleep
Resolved in Pega Version 8.5.1
After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview.
INC-130727 · Issue 573340
Resolved mobile app java.lang.OutOfMemoryError
Resolved in Pega Version 8.5.1
After working with the mobile app for a period, logging in failed and the app crashed with java.lang.OutOfMemoryError exceptions. This was traced to each sync adding a new version of allow-list datapages to the client store which were not cleared, and has been resolved.
INC-135159 · Issue 580675
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-131991 · Issue 583041
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-137352 · Issue 583664
Mobile app improvements for poor connectivity conditions
Resolved in Pega Version 8.5.1
When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.