Glossary

Use the glossary when a Moltaro term appears in the product or documentation and you need the short version before reading the full guide.

Core terms

• Record: one governed business object in Moltaro, such as a request, asset, inspection, warranty case, entitlement, or another object a team manages over time.
• Record type: the category of record. A record type determines fields, screens, relationships, access behavior, and other rules for records of that kind.
• Entity definition: the configuration behind a record type. Configurators use entity definitions to shape records, fields, display values, access, and runtime screens.
• Entity instance: the system term for one record. The Constructor and the public API use entity definition and entity instance where user documentation says record type and record.
• Field: one named value on a record, such as a date, status, amount, user, file, address, or reference to another record.
• Reference: a field that links one record to exactly one other record without merging their identity, history, or access.
• Hierarchy: parent-child structure between records. See Hierarchies and Tree View.
• Parent field: the direct scalar self-Reference selected by a Table Surface as its hierarchy edge.
• Parent Tree View: a Table Surface presentation, including on the entity default, that renders an indexed parent field as lazy root and child sibling pages.
• Effective root: a visible record whose readable parent is absent from the current visible and archive scope.
• Sibling set: roots, or direct children of one parent, sorted and paged independently by the server.
• Ancestor context: a visible nonmatching record kept in a filtered tree only to connect a matching descendant to a root.
• Group By: a separate value-based presentation concept that creates transient groups; it is not Parent Tree View.
• Inverse reference: a field on the referenced side that lists the records whose paired reference points at the current record.
• Association: an entity definition that models a many-to-many relationship; each association record connects one record on each side and can carry its own fields, history, and permissions.
• Board: a governed process surface where work moves through statuses while staying connected to the underlying record or resource.
• Entitlement: a governed right to use, receive, access, or claim something under recorded terms.
• Role: a group of users and permissions used to manage broad access.
• Assignment: a record-specific responsibility fact that explains who owns, handles, reviews, or is accountable for one concrete record.
• Audit trail: governed evidence of important changes, including what changed, who changed it, and when it happened.
• Catalog: a governed hierarchy whose kind determines how its nodes and records are used.
• Classifier: a Catalog kind whose categories provide reusable hierarchical values for explicit Classifier fields on records.
• Classifier category: one selectable value in a Classifier hierarchy. Its parent-child relationship means broader and narrower classification, not a folder, storage location, or access rule.
• Catalog reader: a role assignment that allows a user to discover and browse one Catalog without granting access to the records shown inside it.
• Catalog administrator: a role assignment that includes Catalog read access and allows maintaining that Catalog’s category tree.