How Offline Mobile Works

Introduction

Offline mobile forms in Appian are powerful, allowing you to design forms with cascading dropdown lists, wizards, validations, conditional content, and more. In order to make this possible, we created an offline evaluator that can reevaluate forms without being connected to the server.

This page contains:

• How the offline evaluator handles data.
• How end users will work with offline forms.
• A diagram of the process.

How offline mobile works with data

Generally, when the user accesses a form, it just pulls the data needed from the server in order to display the interface. However, when a user is offline, forms can't communicate with the server to get this information.

In order to create a consistent user experience, offline-enabled forms work the same on Appian Mobile whether the user is offline or online. When you enable a form for offline use, you are changing the way that the form communicates with the server. Instead of being able to talk to the server whenever it wants, it only talks to the server when a form is first loaded and caches the data on the device. After that, it assumes the server isn't there, even if the user is online.

When an offline form is submitted, it always goes to the Pending Forms list in the Appian Mobile menu . If the device is online when the form is submitted, it is sent from Pending Forms to the server right away. If the device is offline, it remains in Pending Forms until the device goes back online. Once online, the form submits automatically.

Syncing data for offline use

While online, users can sync their offline-enabled actions and tasks to make sure they are using the most up-to-date interfaces, processes, and data. Users will need to remain online long enough for the data to sync successfully. The amount of time required will depend on the strength of the device connectivity and the amount of data being synced.

Triggering an offline data sync

The best way to sync data is by triggering an offline data sync from the mobile menu. This will sync all offline interfaces, processes, and data.

To trigger an offline data sync:

1. In Appian Mobile, open the mobile menu.
2. Tap Data Sync.
3. Tap START SYNC.
4. Remain online until the sync completes.

Other methods to sync data

Before going offline, we recommend that users trigger an offline data sync to ensure everything syncs successfully and they can work disconnected with confidence.

However, data is also synced in the following ways:

• Receiving a push notification for a new task. Receiving a push for a new task while online triggers a sync for all offline tasks.
• Syncing automatically in the background. Every 2 hours, a background fetch will attempt to sync the data for all offline actions and tasks. This fetch is dependent on the operating system's prioritization of background processes and is not guaranteed. Additionally, to be successful, when the fetch occurs:
  • The user must be online.
  • Appian Mobile must be running in the background, not force closed.
• Signing in to Appian Mobile. Any time a user signs in to their account, the data for all offline actions and tasks will sync.
• Loading the mobile site task list or the Tasks or Actions Tempo page. When the user navigates to one of the following locations in Appian Mobile while they are online, the data for offline tasks or actions will sync.
  • Opening the mobile site task list will sync all offline tasks.
  • Opening the Tasks page in Tempo will sync all offline tasks.
  • Opening the Actions page in Tempo will sync all offline actions.
• Pulling to refresh. Offline data on an action or mobile site task list will sync any time the user is online and pulls to refresh the page. If you are using a custom task list, we highly recommend triggering an offline data sync instead of relying on the pull to refresh behavior to ensure everything syncs successfully.

Offline flow for users

To ensure users are getting the most up-to-date data, they should be coached about how to use offline forms.

The most important steps that users should be aware of are:

1. Make sure the Appian Mobile application is up to date.

   Note:  For offline mobile capabilities to work, the Appian Mobile application on the user's device must be the same version or newer than the Appian environment.

2. When online, trigger an offline data sync to download the latest interfaces, processes, and data to the device. Remain online until the sync completes.
3. Complete and submit the form as normal, whether offline or online.

   • If the user is offline when they submit the form, it will queue the form for submission. The user can access the form in the navigation menu under Pending Forms. After they go back online, the form is submitted automatically.

     

   • If they are online when they submit the form, the form submits right away.

     Tip:  Sometimes when a pending form fails to submit, a retry icon displays on the Pending Forms list. The user can tap the icon to retry the form submission.

     

Offline mobile diagram

The following diagram shows how offline mobile forms are evaluated.

Step	Description
Initial evaluation on the server	During an offline data sync, the data queries and partially compatible functions that are loaded in local variables at the top of the parent interface are downloaded and cached onto the mobile device.
User input	Whether the user is offline or online, they enter information into the offline interface using the mobile device.
Offline reevaluation	The data on the interface reevaluates based on the user input. The user does not need to be online for this reevaluation to occur. Only Compatible and Partially Compatible functions in the Appian functions table are supported in offline interfaces. If you need to use Partially Compatible functions, you will need to load them in a local variable at the top of the interface.
User input stored	The user input is stored on the device. If the user is offline, their action or tasks goes into a pending state.
Form submitted	When the user has an online connection, the action or task is submitted. The server replays all user interactions to ensure consistency, then moves to the next node in the process model, such as the write records smart service.

Feedback