Two different levels of offline:
Built-in semi-offline:
The fat clients only need connectivity when passing a cogwheel.
Seed inbox items are downloaded and can be accessed without connectivity.
Less network dependency and better mobile performance.
Push cogwheels to the start and end events ? and you can be offline in between.
Constant offline:
Offline Resources are used for supporting data (User Info, Equipment Structures, Lists etc.)
Machine Swimlanes executes cogwheels on the server.
A background job on the client handles data and transactions whenever there is connectivity.
The user do not have to think about going online or offline.
Last updated 6 years ago
Was this helpful?
