The RFID Tags 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-tags) gives tenant administrators a focused workspace for seeding and managing EPC (Electronic Product Code) tags against their warehouse item catalog. It is designed primarily to support end-to-end testing of the handheld RFID scanning flow — allowing you to create individual EPCs, bulk-import lists via paste, link tags to real items, and confirm resolution before going live with production hardware.
Access to this screen is scoped to the ADMIN module. Only users with a tenant-admin role can create, import, or deactivate EPC tags. All operations are isolated to the authenticated tenant.
Object Types
Each EPC tag must be assigned an object type that describes the physical unit of measure the tag is attached to. Dragon Guard WMS supports the following object types on this screen:| Object Type | Description | Available in This Screen |
|---|---|---|
ITEM_UNIT | A single scannable unit of an item | ✅ Fully usable |
CASE | A case or carton containing multiple units | ✅ Fully usable |
PACK | A pack or inner pack | ✅ Fully usable |
PALLET | A pallet load | ✅ Fully usable |
BIN | A warehouse bin location | ❌ Blocked |
LOCATION | A zone or named location | ❌ Blocked |
Creating a Single EPC Tag
Click New Tag to open the create dialog. Fill in the required and optional fields:| Field | Notes |
|---|---|
| EPC | The primary EPC identifier string for the tag |
| Raw EPC | The raw hex or binary EPC value (optional) |
| Item | Autocomplete lookup against the tenant item catalog |
| Object Type | One of the usable types listed above |
| Quantity | Numeric quantity encoded in the tag |
| Status | Tag status enum (e.g., active, reserved, in-transit) |
Bulk Import
For test seeding or large initial loads, use Bulk Import to paste multiple EPC values at once rather than uploading a file.Import Dialog Fields
Batch Settings| Field | Description |
|---|---|
| Batch Reference | A label to group this import batch for traceability |
| Remarks | Free-text notes about the import |
| Continue on Error | When enabled, the import proceeds past invalid lines instead of aborting the entire batch |
| Allow Updates | When enabled, existing EPCs in the system are overwritten with the new values; when disabled, duplicates are rejected |
| Field | Description |
|---|---|
| Item | Autocomplete — all pasted EPCs will be linked to this item |
| Object Type | Applied uniformly to every EPC in the batch |
| Quantity | Quantity value encoded for each tag |
| Status | Initial status assigned to all imported tags |
Batch Result Table
After the import completes, a per-line result table is displayed inside the dialog:- Line — original line number from the paste area
- EPC — the EPC value from that line
- Result —
success,skipped,error - Message — backend detail for failures or skipped entries
Filtering Tags
Use the filter bar above the table to narrow the tag list. Filters act as an intersection (all applied filters must match):| Filter | Description |
|---|---|
| EPC | Partial or exact EPC string match |
| Item | Filter by linked item code or description |
| Lot | Filter by lot number |
| Serial | Filter by serial number |
| Status | Tag status enum value |
| Object Type | One of the five object type values |
| Active State | See active state filter section below |
Active State Filter
The active state filter has three modes:| Mode | Behavior |
|---|---|
| Active Only | Returns only active tags (backend-native filter) |
| All | Returns all tags regardless of active state |
| Inactive Only | Returns only inactive tags — client-assisted: the backend only exposes activeOnly; the frontend fetches all records and filters inactive tags locally |
When using Inactive Only, be aware that the result set is filtered client-side after fetching all records. For very large datasets, consider using the All mode and sorting by the Active column instead.
Table Columns and Row Actions
The main table displays the following columns:| Column | Description |
|---|---|
| EPC | The tag’s EPC identifier |
| Item | Linked item name or code |
| Lot / Serial Hint | Lot number or serial number associated with the tag |
| Object Type | The object type assigned at creation |
| Quantity | Encoded quantity value |
| Status | Current tag status |
| Active | Boolean active/inactive indicator |
| Last Seen | Timestamp of the most recent RFID scan event for this tag |
| Action | Description |
|---|---|
| Detail | Opens a read-only detail dialog showing all tag fields and metadata |
| Copy EPC | Copies the EPC string to the clipboard for use in handheld tests or other forms |
| Deactivate | Marks the tag as inactive; the row remains visible in the All and Inactive Only filter modes |
End-to-End Test Flow
Use the following steps to validate a complete RFID scan cycle from tag creation to item resolution:Open the RFID Tags Screen
Navigate to
/dashboard/admin/rfid-tags. Confirm you are authenticated as a tenant admin.Create an ITEM_UNIT EPC
Click New Tag. Set the object type to
ITEM_UNIT, select a real item from the autocomplete, assign a quantity, and provide a recognizable EPC string. Save the tag.Copy the EPC
Locate the new tag in the table. Click the Copy EPC action to copy the EPC string to your clipboard.
Scan with the Handheld App
Paste or program the copied EPC into your RFID handheld device and perform a scan within the relevant WMS workflow (e.g., Item Inquiry, Receipts).
Confirm Resolution in Item Inquiry
Open the Item Inquiry screen and verify that the scanned EPC resolves to the correct item you linked in step 2.
API Endpoints
All endpoints are tenant-scoped and accessed viaWmsService.
| Method | Endpoint | Description |
|---|---|---|
GET | /api/rfid/tags | List all tags with optional filters |
POST | /api/rfid/tags | Create a single new EPC tag |
POST | /api/rfid/tags/bulk | Bulk import EPCs from a paste payload |
GET | /api/rfid/tags/{id} | Retrieve full detail for a specific tag |
PUT | /api/rfid/tags/{id}/deactivate | Deactivate a tag by ID |
Edge Cases
Bulk import with an empty paste area
Bulk import with an empty paste area
Submitting the bulk import dialog with an empty EPC text area will be rejected immediately. The import requires at least one non-blank EPC line to proceed.
Mixed valid/invalid lines with Continue on Error enabled
Mixed valid/invalid lines with Continue on Error enabled
When Continue on Error is
true, the backend processes each line independently. Valid EPCs are created, invalid ones are recorded as errors in the batch result table, and the overall import is marked as a partial success. Check the per-line result table for full details.Duplicate EPCs when Allow Updates is disabled
Duplicate EPCs when Allow Updates is disabled
If Allow Updates is
false and a pasted EPC already exists in the tenant catalog, that line will be rejected with a duplicate error in the batch result table. The rest of the batch is unaffected when Continue on Error is also enabled.BIN and LOCATION object types are blocked
BIN and LOCATION object types are blocked
These types appear in the object type dropdown to match the backend enum, but they cannot be saved from this screen. The backend will reject them because
CurrentBinId and CurrentLocationId are required fields that are not present in the RFID Tags form.Partial success in bulk import
Partial success in bulk import
A batch can complete with a mix of successes and failures. The batch result table displays a row for every pasted EPC line, with its individual
success, skipped, or error status and a descriptive message. Review all lines before assuming the entire import succeeded.