Introduction
This article is a brief introduction to using the Halo app offline. It is planned to be part of a larger article on surveying a job.
When a user plans a device, the Halo app goes offline. When the user taps Save, the app tries to connect to a network to upload the data. In some cases, manual upload is required.
Planning a survey job offline
Start surveying
When a user opens a machine or node, via the site survey job, and starts surveying, the Halo app disconnects from the network.
Upload data automatically
When the user taps Save, the data is saved to the device, including any changes made to internal pages. If there is a network, the data is uploaded. This is repeated for each planned device.
The data is uploaded if a network is found. Otherwise, the data is queued for upload and the app automatically tries to connect to a network again. In the meantime, any additional completed device data is added to the queue.
You can see the list of devices awaiting upload in a new section above the list of nodes and machines.
Next to each device is the status of the upload (awaiting, in progress, and failed). Once the upload is complete, the device is removed from the list.
Upload data manually (if upload fails)
If there is a problem uploading the data, the app stops the automatic retries to connect to a network. In such a scenario, the user needs to tap Upload data when they are connected to a network to complete the upload.
IMPORTANT - Don’t exit the survey job before the data upload is complete.
If the user tries to exit the survey job while there is still device data that hasn’t been uploaded, they are asked to reconsider. If they continue, the data is deleted and cannot be recovered.