Configuration

Use configuration documentation when you are shaping a Moltaro application for a real team: deciding which record types exist, how they relate, which screens users need, how access works, and how data moves in and out.

Configuration is where a generic platform becomes an operational system. Good configuration keeps daily work understandable, governed, and adaptable without turning every change into custom development.

Start here when a user-facing topic turns into setup work.

Model data

• Data structure — define entity definitions, fields, relationships, templates, catalogs, classifiers, and containment.
• Record search — choose the direct and related content searched for each record type.

Configure record behavior

• Reference Eligibility — validate and enforce candidate constraints for Reference fields.
• Hierarchy Selector — configure guided selection across related hierarchy levels.
• Manual Order — configure one durable relative order across Flat and Tree Table Surfaces.

Configure screens and navigation

• Card item layout — choose responsive widths for Card fields, text blocks, and alerts, with the same authored intent in Drawer and Details.
• Form Related tables — embed an independently saved child-record table from one direct inverse relationship, with role-aware child Table Surface selection.
• Hierarchies and Tree View — model parent-child records and configure secure, sortable Parent Tree View surfaces for lists, related tables, and Reference Lookup pickers.
• Table filters and sorting — define available filters, sort choices, and default ordering.
• User menus — role-targeted navigation menus resolved per user at runtime.

Configure expressions and rules

• Expression language (DSL) — syntax and reference material for field behavior, presentation rules, statements, validation, eligibility, and calculated fields.
• Business logic — choose between declarative configuration and trusted C# when configuration alone is not enough.