Linear View
Linear view lays a register's activity out along time, so you see a shift as a sequence rather than as a list of rows.
What it is for
A grid answers "which transactions match?" Linear view answers "what was this register doing?"
Those are different questions, and the second is the one you have when investigating a period rather than a transaction. Patterns that are invisible in a sorted grid — a cluster of voids in one ten-minute window, a gap where a register should have been busy — are obvious laid out along time.
Reading it
Transactions appear in order along the timeline, with their type distinguishable at a glance. What you are looking for is rhythm and its interruption:
| Pattern | Often means |
|---|---|
| A cluster of voids in a short window | Worth opening — something happened there |
| A gap during trading hours | A break, a closed register, or activity not being recorded |
| Regular activity that suddenly changes character | A shift change, or a change in practice |
Alongside the video
Linear view is at its most useful beside the camera covering that register, with the two aligned in time. You are then reading the transaction record and watching what produced it together, which is considerably faster than checking each transaction individually.
Open the camera in a pop-out on a second monitor, or use the video grid with players kept in sync.
Choosing a period
Long enough to establish what normal looks like, short enough to see detail. A shift is usually right; a week is not.
If you do not yet know which period to look at, do not start here. Aggregate first to find the register and the day, then come to linear view for the detail.
Where it leads
Selecting a transaction opens its receipt, and from there the video and the employee. Each step is captured in your Workspace.
Audit record
What eConnect writes to the audit trail for the actions on this page.
QUERY 'POS Events' FROM {start date} TO {end date}; VIEW: 'Events' PAGE {page};