Change History
The Change History page is an append-only log of configuration changes: who changed which setting, when, and which fields moved, with their values before and after. Entries cannot be edited or deleted from the UI.
Change History is separate from Security Events. Security Events answers "who signed in, whose credentials changed, whose access changed": authentication, identity, and policy-change questions. Change History answers "what did this piece of configuration look like before, and who changed it": the operational, day-to-day settings that keep your integrations and communications working correctly.
Access
The page requires the View Audit Logs permission. This is granted to the Admin role by default. Find it on the Change History tab of the Audit page.
What is recorded today
Tagnet records changes to:
- Message templates: created, updated, rolled back, deleted
- Connection profiles: created, updated, duplicated, deleted
- Integration endpoints: created, updated, duplicated, rolled back, deleted
- Devices: created, updated, activated, deactivated, deleted. This includes reader configuration changes (Zebra FX settings, Impinj R700 reader configuration), group membership, and turning event delivery on or off
- Device groups: created, updated, deleted
- Types (item types, device types, location types, transaction types): created, updated, duplicated, deleted
- Workflows: created, updated, duplicated, enabled (Activated), disabled (Deactivated), deleted, and scope changes
- System settings (instance name, terminology): created, updated. The Change history link at the bottom of the System Settings tab opens the log filtered to them
A copy of a connection profile, integration endpoint, type, or workflow is recorded as Duplicated, not Created, and names the source it was copied from, so filtering on Duplicated finds everything cloned from an existing definition. A copied workflow's entry also lists the settings, conditions, and actions it started with.
For a reader configuration change, an Impinj R700 entry lists which settings changed; a Zebra FX entry shows each changed setting's value before and after.
Starting or stopping a reader, heartbeats, and a deployment writing back the configuration it just pushed are not recorded here: they aren't configuration changes. When someone starts a reader operation that changes the device (for example, pausing event delivery from Reader control), the entry is attributed to that person, even though Tagnet completes the operation in the background.
Type entries include settings that change behavior, not just name, icon, and color: an item type's quantity tracking and identifier strategies (the Instance ID and Tag ID sequence generators show by name, not by internal id), and a transaction type's code and its "Removes from inventory" lifecycle effect.
What Quick Import creates (item types, a default location type, custom fields, and locations) is recorded with the action Imported rather than Created. All entries from one import share the same correlation id, so you can see everything that import created together. Imported custom fields and locations appear in this log; their later edits are not recorded yet.
A workflow update shows its settings (name, trigger, event, scope) as ordinary before/after fields. Its event conditions and tag conditions each appear as one row: whatever conditions you removed show under Before, whatever you added show under After, so changing a single condition shows just that one, and saving without changing any records nothing. A device, device group, device type, or scope referenced in an event condition shows by name, not by id. Each action appears as "Action › <name>": adding an action shows its type under After, removing one shows its type under Before, and editing an action shows each changed setting on its own row, for example "Action › Notify › Configuration › Title template", including its run condition, "Runs after" dependency, evaluation order when actions are reordered, and its own conditions.
Reordering workflows, by dragging them in Reorder mode or with Move to position… on the Workflows list, records one entry per workflow whose position moved, showing its sequence before and after; all the entries from one reorder share a correlation id.
More areas, such as locations, read signatures, and custom field definitions, are being added over time. If you change something and do not see it here yet, it may not be covered by Change History yet.
Reading the list
Each row shows:
| Column | What it shows |
|---|---|
| When | Timestamp, in your local time |
| Action | Created, Updated, Rolled back, Duplicated, Deleted, Imported, and similar |
| Entity | The kind of thing that changed (Message template, Connection profile, Integration endpoint) |
| Name | The item's name at the time of the change |
| What changed | A one-line summary of what moved |
| Changed by | Who made the change |
Click a row to open the full detail page, including a field-by-field Before/After table. A field with no value shows as "(empty)".
Versioned items
Message templates and integration endpoints keep a full version history of their content. The Change History entry shows only which version the change moved to, for example "Version 1 → 2" or "Rolled back to version 1 (saved as version 3)". The content itself lives in the item's own version history, not in the audit log.
Not every change creates a new version. Renaming an item or editing its description shows up as a field change with no version number attached, so you can tell "someone renamed this" apart from "someone changed what it actually sends."
Secrets are never recorded
Change History never stores secret values. When a credential or token changes, the entry shows "Secrets changed: <field name>", naming only which field changed, never its value. Other fields that can hold credentials show "Changed (value hidden)" instead of the before and after values. Long text, such as an inline request body template, shows as changed along with its character count rather than the text itself.
This applies to workflow actions too: an API key, bearer token, or header value in a Send HTTP Request or HTTP Integration action's configuration shows as "Changed (value hidden)", and a long inline request body shows as changed with its length rather than its contents.
Note: A save that doesn't actually change anything writes nothing to the log. Change History answers "what changed," not "was Save clicked" or "did an integration call run."
Filtering
Use the filter bar to narrow the list by:
- Entity: message template, connection profile, integration endpoint, and so on
- Action: Created, Updated, Rolled back, Duplicated, Deleted, Imported
- Changed by: a specific user
- Date range, in your local time
- Search: free text across name, entity, and id
Filters persist as you move around the app, so returning to the page keeps your last selection.
History of one item
Open any entry for the item, then choose All changes to this... from the entry's Actions menu to filter Change History to that one item. This works even after the item has been deleted: entries keep the name the item had at the time, so a deleted connection profile or template still shows up under its own name.
For a device, device group, type, or workflow, the item's own detail page has a Change history tab that gets you there directly; see below.
Change history on an item's own page
Devices, device groups, item, device, location, and transaction types, and workflows have a Change history tab on their detail page, visible to users with View Audit Logs. It lists that item's changes newest first, in the same table as the Change History page; click a row to open the change's before/after detail, and Back returns you to the tab. On a type's page the tab sits next to a new Overview tab; on a workflow's page it sits alongside Overview and Analytics. Users without View Audit Logs see the page as before, without the extra tab.
Changed by
The Changed by column shows:
- The user who made the change
- An API key, labeled as "
<key name>(API key)" - System, for changes Tagnet made automatically rather than a person
Correlation id
The detail page shows a correlation id. When a single action produces more than one entry, they share the same correlation id, so you can see everything that moved together.
Retention
Change History rows are kept for 2555 days (7 years) by default, from when the change happened. This is small data: each entry is roughly 1-2 KB, so a busy site making 100 changes a day adds about 70 MB a year. The window is configured on the Retention / Audit policy; see Audit retention. Lengthening the window costs a small amount of disk; shortening it permanently deletes older entries on the next retention run.