Skip to content

Device Detail Page

The detail page of a device is the entry point to almost every process attached to it. It opens from the inventory list via the asset number or the arrow at the end of the row.

Its layout follows the same anatomy as every other detail page in calServer v2: a header with actions, below it a summary row that stays visible on every tab, and then the tabs — first the object itself (Overview), then its processes.

Summary row

Between the header and the tab bar sits the summary that answers the everyday question without opening a tab:

Item Meaning
Calibration status State taken from the active calibration
Due date Next calibration date, with a due marker
Location Where the device was last booked
Open tasks Notes and tasks pointing at this device

It remains visible while switching between tabs.

Tabs

Tab Content
Overview Master data, images and documents, owner and holder, device set, test requirements
Calibrations All calibrations of the device, switchable to the measurement history
Documents Linked DMS documents, including imported calibration certificates
Location history Movements of the device, with a return function
Repairs Maintenance and repair records
Tickets Support cases for the device
Orders Bookings and order items
Change history Audit trail of the record

The count on a tab comes from a dedicated counting endpoint and counts within the same visibility scope the list behind it shows. A number that counts something other than its own list cannot arise this way.

Empty tabs disappear — but not all of them

Tickets and Orders are only rendered when there is something to show; they are read-only here, so an empty tab would offer nothing. Tabs with a create action always remain, otherwise the empty tab would take the only way to fill it with it.

The active tab is part of the URL (?tab=), so a shared link opens the same view. Without it, the overview opens. If a link points to a hidden tab, the page falls back to the overview.

Actions

Editing does not happen on the page itself but in a dialog opened via Edit. The remaining actions sit in the menu next to it:

Action Effect
Edit Opens the device edit form
Reports The reports and labels released for inventories
Create task Creates a note referring to this device
QR code Shows the device QR code, see below
Duplicate Creates a copy
Import MET/TEAM call sheets Only with a configured MET/TEAM connection
Delete Removes the record

Duplicate can be disabled

If the setting "prevent duplicate asset numbers" (disable_double_asset_number) is active, Duplicate is not offered: a copy would carry the same asset number.

QR code of the device

QR code in the menu renders the code as SVG and offers it for download. It points to the deep link of the device (/v2/qr/{uuid}), so whoever scans it lands directly on this record.

The same link is supplied automatically to label and certificate templates, so a printed label carries the code without anyone having to insert it.

Disabled QR links never print into the void

When QR links are switched off in the settings, the report data set no longer contains a URL. A label can therefore never be printed with a link that leads nowhere. The dialog on this page still shows the code — it is a look at the record, not a print product.

To let people open the link without signing in, the QR role is required: see QR code role.

See also