Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

Offline Mobile Design Guidance

Certified Associate Developer

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:

  1. Load application and any data that will be needed for the entry form
  2. Go offline
  3. Invoke form to enter data with any ref data populated from Step 1
  4. Enter data
  5. Submit the form to save changes locally
  6. Go online and see the newly created record

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:

  • Enable offline mobile in Admin Console
  • Enable interface for offline
  • Use CDTs
  • Call data at the top of the parent interface
  • Don't use functions/components that aren't compatible with offline

  Discussion posts and replies are publicly visible