You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing docs@inductiveautomation.com.
LESSON LIST
-
8:15Event Streams
-
3:59Kafka - Source Example
-
3:46Kafka - Handler Example
-
7:58Form Component - Structure and Widgets
-
3:39Form Component - Contingent Actions
-
4:55Form Component - Submission Management
-
4:21Form Component - Submitting Form Data in Offline Mode
-
13:37Form Component - Basic Form
-
2:13Offline Submissions
-
4:19File Association and Deep Links
-
11:38Drawing Component - Overview
-
16:14Drawing Component - Elements
-
5:05Drawing Component - Modification Tools
-
10:43Drawing Component - Layering and Alignment
-
2:14SQL Historian
-
4:55Deployment Modes
-
5:29Siemens Symbolic Driver - Browsing
-
4:46Siemens Symbolic Driver - Migrating
-
4:18Internal Secret Providers - Referenced Secrets
-
1:35Internal Secret Providers - Embedded Secrets
-
7:05Alarm Metrics Filtering and Aggregation
LESSON
Offline Submissions
Description
Let's dive into Offline Submissions' functionality using the browser and the developer tools to find out what happens when an offline form submission fires.
Video recorded using: Ignition 8.3
Transcript
(open in window)[00:00] So how do offline form submissions really work? Let's dive into their functionality using the browser and the developer tools so y'all can get a sense of what's happening under the hood when an offline form submission fires. If you haven't already, please be sure to watch all the videos in the form component topic to get the full context before viewing this supplemental video. I'm using Chrome's toggle device toolbar to show the device and the developer tools side by side in this view. We'll be able to see the data flow from the form into the file system from here. I've already enabled offline mode, so I'll turn off the internet connection in the network tab to simulate a remote environment with no connectivity. Let's add in the necessary info to our form first. Now, we're ready to submit our data and we're completely offline with no connection to the gateway at all. I'll click on submit, and we get a helpful toast message that the form data will be submitted when the connection is restored.
[01:04] If we explore the application section in the developer tools, we can find out where that data went. If you're offline when you submit form data, it gets stored temporarily on the device's file system. I'll just dig down into IndexedDB and the special perspective_submissions_store. The JSON sits in this secure, dedicated application sandbox waiting for the connection to return. Here, you can see how Ignition packaged up the form data neatly for us, along with other useful context and information that we can explore. I'll just turn our internet connection back on quickly, and the form data that the native device stored for us gets submitted successfully. It passes in our form data as a parameter for handling the submission based on whatever submission management settings we've set up for our form. From this browser example, you can see how offline mode makes it easy to store form data on a device when there's no internet connection available. Then, once users get back online, Ignition automatically grabs that data from the local file system and delivers it to its intended destination.