Event History Widget
Event History shows recent events as a live list, newest first. Where a Graph tells you the shape of things, this tells you what just happened.
Configuring it
Point it at a saved query defining which events matter, and name it for what it is watching.
Keep the query tight. A list showing everything is a list nobody reads; one showing only exceptions — voids over a threshold, detections of tagged subjects — is one people actually watch.
What it is good at
- Awareness. Something happened, and here it is, without anyone running a query.
- Context beside a chart. A Graph showing a spike, with an Event History beside it showing which events made it, is a genuinely useful pairing.
- Handover. Starting a shift by reading what happened on the last one.
Clicking through
Rows open the event behind them, so the widget is a way into the data rather than only a display. Following a row is a drill like any other and is captured in your Workspace.
That is the main reason to prefer this over a static list: the interesting event is one click from its full record.
Clearing a backlog of pending reviews
The widget's Pending Review dialog lists what is waiting, a tab per kind of event. Three controls act on it:
| Control | What it does |
|---|---|
| Review Event | Opens one row's event for review |
| Review All Pending | Opens the whole tab's events as a single query, scoped to the period they cover |
| Mark All as Reviewed | Clears the tab without opening anything |
The middle one is the one to reach for on a shift handover. It gives you every pending event of that kind in one grid — which is a review rather than a queue of dialogs — and leaves the marking until you have actually looked.
Mark All as Reviewed makes no claim to have looked. Use it when the backlog is known noise, and be aware that the clearing is recorded against your name either way.
Sizing it
Give it enough height to show several rows. A widget showing one row at a time is a ticker, and it will be missed.
Widen it if the event descriptions are being truncated — a list of half-sentences is unreadable.
Refresh
The widget updates as events arrive, so a dashboard left open on a wall stays current with no interaction.
Not the same as alerts
Event History shows events; alerts demand a decision and are recorded as acknowledged or ignored.
Use Event History for awareness of things that do not need action. Use alerts for things that do — a row scrolling past on a dashboard is not a record that anybody saw it, and cannot be reviewed later as one.
Audit record
What eConnect writes to the audit trail for the actions on this page.
DASHBOARD CONFIGURE WIDGET '{name}' SAVED