Skip to content
Moltaro Docs

Record types

A record type is the category of business object a record belongs to. Examples might include Asset, Service Request, Inspection, Warranty Case, Customer Resource, Production Item, Contact, or Contract.

Each record belongs to one record type. The record type determines what the record means, which fields it has, how it is displayed, what related information is expected, and which rules apply.

Why record types matter

Section titled “Why record types matter”

Record types let Moltaro match the shape of the system to the shape of the operation. A service request needs different information than an asset. A warranty case needs different context than a contact. A production item may need different process and history than a reference-data list.

Because record types are configured separately, each type can have its own:

  • singular and plural names;
  • fields and field types;
  • required or read-only values;
  • default display values;
  • relationships to other record types;
  • comments, files, tags, search, or audit settings;
  • access model, permissions, assignments, and field visibility rules;
  • screens, forms, lists, cards, drawers, and other UI surfaces.

Users do not need to know every configuration detail to work with records, but they will notice that different record types behave differently.

Record type vs record

Section titled “Record type vs record”

A record type is the definition of a kind of thing. A record is one actual thing of that type.

For example:

  • Asset is a record type.
  • Forklift FL-204 is a record.
  • Warranty Case is a record type.
  • Case WC-3817 for Forklift FL-204 is a record.

This distinction helps when reading documentation. Pages about records explain daily use. Pages about record types and entity definitions explain how the system is configured.

Configuration bridge

Section titled “Configuration bridge”

Administrators and configurators manage record types through entity definitions. An entity definition is the configured description of a record type: fields, relationships, display behavior, access model, history settings, and runtime UI surfaces.

Most user documentation says record type because that is the concept users see in lists and detail pages. Configuration documentation uses entity definition when the topic becomes administrative or technical.

Where to go next

Section titled “Where to go next”