The RFID Events screen (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_WEB/llms.txt
Use this file to discover all available pages before exploring further.
/dashboard/admin/rfid-events) is the tenant-scoped audit trail for every RFID read that the Dragon Guard WMS backend has captured and persisted. Warehouse administrators and integration engineers use this screen to inspect individual scan events, trace document associations, review resolution and validation outcomes, and investigate failures — all without requiring direct database access. It is the primary diagnostic surface for RFID workflows in production and testing environments.
Access to this screen is scoped to the ADMIN module. All events displayed belong to the authenticated tenant. Cross-tenant event data is never exposed.
Available Filters
The filter bar supports a rich combination of criteria. All active filters are applied as an intersection — a row must satisfy every active filter to appear in the results.- Content Filters
- Correlation Filters
- Date Range Filters
| Filter | Description |
|---|---|
| Free Search | Broad text search across EPC values, item snapshots, and document references |
| Module | The WMS module that generated the event (e.g., Receipts, Shipments, Movements, Inquiry) |
| Resolution Status | Outcome of the backend’s attempt to resolve the EPC to a known item or tag |
| Validation Status | Outcome of rule-based validation applied to the resolved scan |
| Document Type | The type of warehouse document the event is associated with |
| Document Number | Exact or partial document reference number |
| Errors Only | When enabled, restricts results to events that have an error in either resolution or validation status — not only events with a populated ErrorMessage field |
Table Columns
The events table surfaces the most operationally relevant fields at a glance:| Column | Description |
|---|---|
| Scanned At | Timestamp of the raw RFID read event captured by the backend |
| Module | The WMS module context in which the scan occurred |
| Event Type | Backend classification of the event (e.g., scan, re-scan, manual entry) |
| EPC | The Electronic Product Code value captured by the reader |
| Item Snapshot | A point-in-time snapshot of the item matched to the EPC at the moment of the scan |
| Resolution Status | Whether the backend successfully resolved the EPC to a known item or tag |
| Validation Status | Whether the resolved scan passed the applicable rule-based validations |
| Document Snapshot | A snapshot of the associated warehouse document at the time of the event |
Detail Dialog
The detail dialog displays the complete stored payload for a selected event. Because there is no dedicatedGET /api/rfid/events/{id} endpoint in the current phase, the dialog renders directly from the row’s list payload — no secondary network request is made.
Sections
Capture Context
Capture Mode, Operator, Device Snapshot — who scanned, with what device, and in what capture mode (e.g., automatic antenna, manual trigger).
Location & Bin
Location Snapshot and Bin Snapshot representing the physical position of the reader or operator at scan time.
Rule & Mode
Applied Rule — the RFID policy rule that was evaluated for this event. Effective Mode — the resolved operating mode (e.g., strict, lenient, manual-fallback) that was active.
Error & Metadata
Error Message — populated when the event resulted in a hard error. Metadata JSON — raw backend metadata blob rendered inline; malformed or plain-text values are displayed as raw text without breaking the dialog.
The errorsOnly Filter
The Errors Only toggle behaves more broadly than its name suggests. It surfaces rows that have an error condition in any of the following:ResolutionStatuscontains a failure or unresolved valueValidationStatuscontains a failed or warning valueErrorMessageis populated
ErrorMessage is empty, as long as resolution or validation did not succeed. Use this filter to get a complete picture of problematic scans, not just those with explicit error messages.
Current Constraints
| Constraint | Detail |
|---|---|
| Enum labels | Resolution status and validation status values are rendered as raw backend technical enum strings. Not all values have been mapped to user-friendly display labels yet. |
| Date filter timezone | From and To datetime filters are sourced from browser datetime-local inputs and sent to the API as ISO 8601 UTC strings. The display reflects local browser time; the stored events use server UTC. |
| No per-event GET endpoint | The detail dialog renders from the list row payload. If additional fields are stored in the backend but not returned by the list API, they will not appear in the dialog until a dedicated detail endpoint is added. |
API Endpoint
Events are retrieved via a single endpoint, accessed throughWmsService:
| Method | Endpoint | Description |
|---|---|---|
GET | /api/rfid/events | Retrieve a filtered, paginated list of RFID scan events for the authenticated tenant |
Edge Cases
Free search and status/module filters behave as an intersection
Free search and status/module filters behave as an intersection
Entering text in the free search field while also selecting a module or status filter does not perform an OR union. All active filters must be satisfied simultaneously. Clear individual filters to widen results.
errorsOnly can match rows without an ErrorMessage
errorsOnly can match rows without an ErrorMessage
An event is included in errorsOnly results if its ResolutionStatus or ValidationStatus indicates a failure, regardless of whether the ErrorMessage field has content. Do not assume an empty ErrorMessage means the scan was clean.
Events without CorrelationId or SessionId
Events without CorrelationId or SessionId
Events that were captured outside a tracked session or correlation chain will display a dash (
-) in those columns. This is expected for certain module types or legacy scan events and does not indicate data corruption.Malformed or plain-text MetadataJson
Malformed or plain-text MetadataJson
If the MetadataJson field contains invalid JSON or plain text rather than a structured object, the detail dialog renders it as raw text instead of a formatted tree. The dialog remains fully functional and does not throw an error.
Events with no document association
Events with no document association
Some scan events (e.g., from Item Inquiry) are not linked to a warehouse document. The Document Type, Document Number, and Document Snapshot columns will be empty or display dashes for these events. This is normal behavior for inquiry-mode reads.