We have a use case for a mobile offline application. I'm trying to build a simple app to test the functionality. Are there any other pointers beyond the design guidance in the documentation?
An example of the application process flow is as follows:
The documentation talks about offline actions and offline tasks. I would like to implement offline actions but I'm not seeing much detail on configuring them.
What would be really useful is a working example with a similar flow to what I've described. In that case, I could dissect to fit my use case. Also useful would be more pointed steps for implementing this functionality.
I'm aware of the following:
Discussion posts and replies are publicly visible
Enable Offline Features:
Data Modeling with CDTs:
Preloading Data:
Interface Design for Offline:
Offline Actions:
Synchronizing Data:
Would you please NOT post ChatGPT generated answers without verification! The issue is, that they sound plausible, but are misleading or plainly wrong in the details.
E.g. there is no "IndexDB" in Appian, and there is no explicit offline capabilities in CDTs.
One helpful piece to remember is that functions such as a!documentDownloadLink() and a!processTaskLink() also need to be part of your a!localVariables() set and not used inline within SAIL components as is the normal design paradigm.