Record types
A record type is the kind of event you want to keep: ProductionReport, Fault,
QualityCheck. You create it under Settings › Database, without a new release.
Behind every record type stands a real table in your operational database. TrakState builds it when you create the type, from your configuration. Each customer has their own operational database; the configuration itself lives separately from it and is recorded in the audit trail.
Creating one
Section titled “Creating one”New record type asks only for a Name. The fields come afterwards, in the field grid (see Fields). A name may occur only once within a tenant.
Operational data or master data
Section titled “Operational data or master data”Every record type is either operational data or master data. This is a setting you make — it is never guessed from the name.
| Means | Examples | |
|---|---|---|
| Operational data | a captured event | ProductionReport, Fault, ShiftNote |
| Master data | a reference list belonging to configuration | Line, Station, Shift, FaultReason |
Switching is harmless and reversible at any time: it changes only the classification, never the table and never the stored rows. What master data is for is covered under Value lists.
Renaming and deleting
Section titled “Renaming and deleting”Rename is harmless. Internally the table is named after an immutable id, not after the display name — no schema change runs, and no tag or binding breaks.
Delete record type cannot be undone. TrakState counts first and tells you: how many records depend on it and how many tags read from it. The type takes those tags, its fields and the table with it.
Applying instead of building
Section titled “Applying instead of building”Under Settings › Templates there is a finished configuration for OEE capture: master-data
lists, ProductionReport, Fault, QualityCheck and more, with fields and tags. You can apply
it and then change it like anything else. Nothing already present is overwritten.
Objects from a template
Section titled “Objects from a template”A template from the store (Settings › Templates) creates record types under a namespace of its own,
for example OEE.Downtime. Such record types carry a badge “from
The Origin filter above the list shows all, only those from templates, or only your own. Whether something came from a template is decided by its identity, not by its name: one you create by hand in the same namespace belongs to you, and renaming one from a template keeps the badge. Deleting or renaming is allowed; an update of the template does not create a deleted one again.