Data structure
Data structure is where a Moltaro installation gets its shape. Configurators use entity definitions, fields, relationships, templates, catalogs, and classifiers to model the work people actually do.
This is the configuration-facing section. It uses the same terms the product shows in the Constructor, so what you read here matches what you see on screen.
Terminology bridge
Section titled “Terminology bridge”User documentation and the running product use friendly terms; the Constructor and the API use system terms. They describe the same things:
| User docs say | The Constructor and API say | Meaning |
|---|---|---|
| Record type | Entity definition | The configured shape for a kind of record: fields, access, logic, screens. |
| Record | Entity instance (often just “entity”) | One actual business object of that type. |
| Fields | Schema | The stored field list of an entity definition. |
When you work in the Constructor or call the public API, expect the system terms: the API groups are Entity Definitions and Entity Instances. When you read Data and records, expect the friendly terms.
Where structure is configured
Section titled “Where structure is configured”Data structure lives in the Constructor area of the web app. Its Data model group contains:
- Entity Explorer — the list of entity definitions. Opening one shows the configuration sections documented under Entity definitions.
- Catalogs — hierarchical trees that organize records. See Catalogs.
- Duplicate detection — exact and fuzzy matching profiles that find likely duplicate records. See Duplicate detection.
- Templates — guided starters that create ready-to-adjust configuration. See Templates.
In this section
Section titled “In this section”- Entity definitions — the main guide: schema, projection, location, access, transfer, logic, and UI surfaces of a record type.
- Relationships and containment — references, inverse references, associations, and governed parent-child structure.
- Duplicate detection — configure exact or fuzzy rules and understand complete Details checks, partial bounded Table checks, and durable complete full scans.
- Templates — guided starting points.
- Catalogs — hierarchical organization.
- Classifiers — shared reference values.
Where to go next
Section titled “Where to go next”- Read Data and records for the user-facing view of the same concepts.
- Read Entity definitions to start configuring.
- Use the API reference when an integration or agent needs to read definitions or work with records programmatically.