Offline mode
The GIS lets you handle complaints without a network. Actions taken offline are kept on the device, then sent to the server when the connection returns. The other modules need the network.
What works offline
| Screen | Offline |
|---|---|
| Complaints (GRM) → Complaints | Viewing and full handling, see below |
| Complaints (GRM) → Kobo - Complaints | Categorising submissions already loaded, sent when the network returns |
| Other screens | No: an action shows "This action requires an Internet connection" |
The application cannot reload without a network: a reload shows the "Vous êtes hors ligne" page. Open the GIS and the complaints list before going to the field, and do not close the tab.
Connection indicators
- A bar at the top of the screen announces "Connection lost - Offline mode enabled", then "Connection restored".
- Offline, it shows "Offline mode - Changes will be synced when connection is restored" and the number of pending actions.
- Online, if actions are still pending or failed, the same bar offers Sync now.
- In the header, the red Server unreachable badge means the network works but the server does not answer.
Complaints offline
Complaint handling works without a network from a local copy of the complaints in your scope.
What is copied to the device
- The complaints you are allowed to see, with their comments, workflow phases and attachment descriptions (name, size, type). The file itself stays on the server.
- The reference data needed: projects, regions, sectors, localities, types and categories, assignable agents, workflows.
- The copy is refreshed each time the complaints list opens and each time the network returns.
Sensitive complaints (SEA/SH) are never copied to the device and cannot be handled offline. No sensitive data leaves the server.
Available actions
| Action | Offline | Note |
|---|---|---|
| View the list, filters, details | Yes | Local copy |
| Create a complaint | Yes | Temporary reference LOCAL-…, replaced once sent |
| Take charge, resolve, not eligible, close, reopen | Yes | Same status rules as online |
| Assign, reassign | Yes | Agents from the local reference data |
| Comment | Yes | Marked "Pending" until sent |
| Move to the next phase | Yes | Timeline rebuilt locally |
| Add an attachment | Yes | 10 MB maximum, kept on the device until sent |
| Edit fields | Yes | |
| Download an attachment | No | File on the server |
| Acknowledgement, notification, escalation | No | Sent immediately by email or SMS |
| Delete a comment or a document | No |
Each action applies at once to the local copy, then joins the queue. When the network returns, actions are sent in the order they were made, then the local copy is refreshed from the server.
The server records the date of sending, not the date of offline entry. The local history keeps the real date, marked "offline".
Pending and rejected actions
At the top of the complaints list and of the complaint concerned:
- an orange banner lists actions waiting to be sent, with Send now;
- a red banner lists actions rejected by the server, with the reason. For example, resolving a complaint a colleague has already closed.
For a rejected action, two choices:
- Retry sends the action again as it is;
- Discard deletes it, after confirmation, and the complaint returns to the server's state.
Logging out
On logout, all local data is erased: complaints, reference data and queue. If actions have not been sent yet, the logout window says so in red. Reconnect the device to the network and wait for the sending before logging out.
The queue is shared by all tabs of the same browser. Another tab that is online may send your actions before you do.
Good practice
- Before leaving, open the complaints list online to refresh the local copy.
- In the field, keep the tab open.
- Back online, check that the banners no longer list pending or rejected actions.
- Log out only once everything is sent.
Installed application
In Chrome or Edge, an Install app prompt offers to install the GIS as an application. Later dismisses it.
In the installed application, the Refresh button in the header loads the latest version of the GIS. In a browser, Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) does the same.