LAN Snapshot Tools

Use This Dashboard Area Safely

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, LAN Snapshot Tools narrows that work to surface guide for exporting and importing EMS LAN snapshot files. Because this is a surfaces page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Export operators and Import operators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/offline-snapshot?id=:eventId.
• Records or contracts involved: Offline snapshot exports and Offline snapshot imports.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the EMS LAN situation, the owner, and the exact item involved in LAN Snapshot Tools.
2. Read the current state before changing it: Use /rego/events/manage/offline-snapshot?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Offline snapshot exports and Offline snapshot imports in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook on the LAN Snapshot page.

1. Step 1 - Open the exact screen for the event. Confirm the URL includes ?id=:eventId for the correct event. This prevents wrong-event file operations.
2. Step 2 - Identify what the screen reads and writes. Decide whether the current task is export or import. This keeps the operator on the right card.
3. Step 3 - Use one control at a time. Use Download LAN snapshot ZIP, Download GZIP JSON, or Import LAN snapshot according to the runbook. This calls the hosted snapshot API.
4. Step 4 - Check who or what was affected. Read the status text and do not close the page until the operation result is known. This avoids half-understood file states.
5. Step 5 - Confirm the screen and history agree. Open LAN Sync History and confirm the matching audit entry. This proves the operation was recorded.
6. Step 6 - Leave notes another operator can follow. Label, hand off, reconcile, delete, or archive the file according to the current phase. This closes the surface action.

Controls

Control	Purpose	Record effect
Download LAN snapshot ZIP	Standard export for the LAN app.	Creates export audit history.
Download GZIP JSON	Technical export format.	Creates export audit history.
File picker	Chooses returned LAN file.	No change until import.
Import LAN snapshot	Applies returned LAN state.	Creates import audit history and updates records.

Missing ID behavior

The route must preserve the event ID. If ?id=:eventId is missing or stale, do not export or import.