Layouts and components

Use layout elements to arrange components, and higher-level components to express a workflow. record-browser owns a selectable master list and a detail slot; record-editor loads and edits the chosen record; related-records displays children and can bind their creation form to the selected parent. The reference lists the attributes each one accepts.

For dashboards, kpi-summary collects scalar metrics, metric-panel combines a metric query with summaries and a trend, and trend maps a series to plotted values. Prefer these components over assembling a dashboard from unrelated text blocks. Choose labels and units that explain what each value measures.

For lower-level composition, use panels and the catalog's layout elements. Within forms, sections are unconditional presentation groups. Fieldsets add conditional participation and retained drafts. Both accept one or two columns; case-local sections preserve authored order and do not accept conditions.

Each authored ID must be stable and unique in its required scope. Composite components create their own internal IDs; compiler diagnostics identify collisions. Do not depend on generated internal IDs in authoring source.

The recipe chapter contains complete ERP and dashboard compositions. The reference lists every supported component, attribute, child contract and default. Components not present there are not XML extension points. Custom application code belongs in the separate Custom App feature.