Make Offline Data Persistent for Mobile Devices
Currently offline workflows support downloading data into the client and run workflows without an internet connection. However this data purely reside on memory when it comes to mobile devices.
If the application has to be closed for any reason, whole of the offline data will be lost.
This is essential for situations like off site asset count in remote locations. etc.
-
Samuel Bordelon commented
I agree. Its more of a "snapshot" than offline data. When an end user exits a flow and re-opens is (not paused). even though source data was updated or changed. It re-sets to the original offline state. This seems antithetical to the purpose of offline data. We have end users who have to be offline for a day or more. And if they accidentally close the workflow. They either have to drive hours back into network range. Or trust that the data they input up to that point is stored without any real way to verify it.
-
Does the application close here? I believe offline transactions are saved if the app crashes, however, if a User Logs out purposefully, the transactions are removed from cache. Is this not the functionality you are seeing?