Offline database and unsent changes
The phone reads saved screens with no network and queues edits until it can reach the server. A status pill lists anything still unsent.
What this feature does
The phone reads saved screens from a local database, so a screen opens with no network. Edits wait in a queue until the server can be reached. A status pill lists anything still unsent.
Each queued edit carries a key so it is applied once. Fee payments are the exception: money is not queued offline.
Offline database and unsent changes is on the Mobile app. It is not on the Web portal, Desktop, and Website.
How it flows
- 1Open a screen offline
- 2Make an edit
- 3The network returns
Step by step: how to use it
- 1Open a screen offline
The phone reads the last saved copy.
- 2Make an edit
It waits in the unsent list.
- 3The network returns
The queue sends, and the pill clears.
Quick answers
- What is Offline database and unsent changes?
- The phone reads saved screens from a local database, so a screen opens with no network. Edits wait in a queue until the server can be reached. A status pill lists anything still unsent. It is part of Device and office tools in Paperless Institutes.
- Which apps include Offline database and unsent changes?
- Offline database and unsent changes is on the Mobile app. It is not on the Web portal, Desktop, and Website.
- Who uses Offline database and unsent changes?
- People using the phone with a weak network use Offline database and unsent changes. The phone reads saved screens with no network and queues edits until it can reach the server.
- How does Offline database and unsent changes work?
- 1. Open a screen offline. 2. Make an edit. 3. The network returns.
More in Device and office tools
Layout, cards, and the bottom bar can be changed from the server. The phone and the desktop both draw those screens.
Light, dark, or match-the-device appearance. The phone saves the choice. The portal and the website have a dark theme as well.
The desktop stores the sign-in token with Windows Data Protection, tied to the current Windows user.