Classes & Fields
Define the asset class tree and the typed custom fields each class carries.
Overview
Every asset belongs to a class such as Pump, Generator or Vehicle. A class carries custom fields that its child classes inherit: text, number, date, list, file, reference or yes/no, each with its own rules (minimum, maximum, pattern, length).
Because the class drives the fields, the asset form shows exactly the technical data that matters for that kind of equipment, validated on save.
When to use classes & fields
- You add a new kind of equipment and need its technical data captured consistently.
- You want measurement points defined once per class instead of per asset.
Prerequisites
Step by step
Field reference
| Field | Description | Required | Data type | Business meaning |
|---|---|---|---|---|
| Field type | Kind of value. | Yes | Text, number, date, list, file, reference, boolean | Controls the input and validation. |
| Min / max / pattern / length | Validation rules. | No | Number or text | Values outside the rules are refused on save. |
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- assets.class.read
- assets.class.manage
Automation
- Changes on this screen are written to the asset audit trail and the asset timeline.