Better Offline Data Caching
Today, a customer can download offline data. But if the app crashes, or the user in the field (who is offline) makes changes and then app crashes or they quit out by accident, its confusing to the user as to what has been completed. To the user, it feels like the data has been lost.
An example, lets say I have an offline flow which downloads 10 records in a table. While offline, I add 2 new records to that table, and go to the next step. If the app crashes when the app reopens, and the flow is rerun, the user will only see the 10 records. Not knowing they submitted the 2 additional records. This could be true if they quit out of the app by mistake, instead of the app crashing.
AdminPaul Phillips
(VP Product Management, Novacura)
shared this idea
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Johannes Steger
commented
Another great feature would be to be able to design ONE workflow that is online AND offline, not an online AND an offline version as you need to do today.
Meaning certain data is cached (we need to be able to identify the steps that do this) and automatically refreshed in a configurable intervall. when the user runs a workflow the client should recognize wether it's online or offline and depending on the status either fetch the data online or use cached data. Same would go for any machine steps that execute IFS logic. -
Evaluating feature for Flow Connect.