LAN Sync History

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 Sync History narrows that work to surface guide for reviewing EMS LAN export and import audit history. 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 Event leads and Reconciliation 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-history?id=:eventId.
• Records or contracts involved: Snapshot audit history and Change summaries.
• 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 Sync History.
2. Read the current state before changing it: Use /rego/events/manage/offline-snapshot-history?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 Snapshot audit history and Change summaries 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 to inspect LAN audit history.

1. Step 1 - Open the exact screen for the event. Open LAN Sync History for the correct event ID. This ensures the audit entries belong to the current event.
2. Step 2 - Identify what the screen reads and writes. Check whether you need an export entry, an import entry, or both. This tells you what proof to look for.
3. Step 3 - Use one control at a time. Use refresh, then read actor, action, format, exported time, source metadata, and change summary. This identifies what happened.
4. Step 4 - Check who or what was affected. Compare the audit entry to the file and onsite handoff notes. This catches missing or suspicious operations.
5. Step 5 - Confirm the screen and history agree. Record the audit entry ID or timestamp in reconciliation notes. This anchors the review to evidence.
6. Step 6 - Leave notes another operator can follow. If the expected entry is missing, stop closeout and escalate. This keeps the proof trail intact.

What history shows

Field	Meaning
Action	Export or import.
Format	ZIP, GZIP, or JSON-style snapshot format.
Actor	User who triggered the operation.
Snapshot source	Event and export metadata.
Change summary	Counts and record groups affected.

Operator use

LAN Sync History is the audit trail that lets a future lead answer who exported, who imported, when it happened, and what changed.