Offline Mode
💡Have feedback for this page? Let us know on the IA Forum.
Offline Mode in Perspective allows users to continue interacting with a project even when their device becomes temporarily disconnected from the Gateway. When Offline Mode is enabled, the Perspective module caches necessary project assets locally on the device during initial connection. If a network interruption occurs, users can continue navigating the application and interacting with previously accessed views and their components.
Offline Mode is especially useful for mobile devices, remote installations, and other situations with unreliable connectivity. A project that was opened while connected will continue to run if the device becomes disconnected, but that cached session is limited. You cannot relaunch a project while disconnected, and form submissions will not queue for later delivery. With Offline Mode enabled, the Perspective App stores project resources locally so you can launch projects without a Gateway connection and queue supported interactions such as form submission for automatic delivery once connectivity is restored. This makes it well suited for kiosks, HMIs, and mobile use cases in unstable network conditions.
Offline Mode only works in the Perspective App on mobile devices. It is not supported in desktop browsers.
Enabling Offline Mode​
Offline Mode is configured in the Project Properties panel of the Designer under Perspective > Offline Mode. The following configuration options are available.
Enabled​
Enables Offline Mode for the project when enabled here and on the Manage Application screen in the Ignition Perspective Mobile App. Once enabled, compatible devices running the Perspective App will begin caching project resources.
Security Levels​
Defines which users are allowed to use Offline Mode. You can specify one or more required security levels, such as Authenticated or specific roles.
- All: The user's security levels must match all selected entries.
- Any: The user's security levels must match at least one of the selected entries.
Authentication Token Expiration​
Specifies how long a cached authentication token remains valid for offline access. After expiration, the user must re-authenticate online before offline access resumes. Default is 7 days.
- You can also enable Always ask the IdP to re-authenticate, which forces the user to log in again every time they connect online, even if the token is still valid.
Themes​
Specifies which themes will be cached and available during offline use. Only selected themes will be bundled for offline usage, reducing bundle size.
Available built-in themes include:
- light
- dark
- light-cool
- light-warm
- dark-cool
- dark-warm
If a user selects a theme not listed here, it won’t be available while offline.
Languages​
Specifies which project translations to include for offline use. This setting helps reduce bundle size by limiting localization assets to selected languages.
Using Offline Mode​
When a project with Offline Mode enabled is opened in the Ignition Perspective App, the app caches all necessary project resources locally. This allows users to continue interacting with a project if the network connection drops, and also makes it possible to launch the project without a Gateway connection.
The app provides settings to manage cached projects, delete offline data, and control whether the project should auto-launch offline. For steps on launching and managing projects in the Perspective App, see Ignition Perspective App.
Interaction During Offline Use​
Not all functionality is available while offline. The following limitations apply:
- Realtime values, such as tags, alarms, and queries will not update until a network connection is restored.
- Scripts that rely on Gateway events or database access will not run.
- Views that have not been previously loaded will not be available.
Many UI components remain interactive. In Offline Mode, the Form component queues submissions while offline and sends them to the Gateway once a connection is reestablished. In a cached or disconnected session, form submissions do not queue and will fail if attempted without a connection. Other components that support local event scripts, such as onClick or onChange, will continue to function while offline. Ordering of offline form data submissions may not match the order in which the Gateway receives them, so timestamps should be used when processing or storing form data.
Localization and theme settings should match what’s selected in the Offline Mode project properties. If a user switches to an unsupported theme or language, fallbacks may not be available while offline.