Presentation and statements

Two mechanisms turn record data into consistent user-facing meaning: presentation rules compute each record’s display name and subtitle, and statements name reusable boolean facts.

Display name and subtitle rules

Configured under Display settings on the entity Overview tab. Each target (display name, subtitle) has an ordered rule list; rules are evaluated in order, and the first matching rule wins.

A rule has one of three modes:

• Field — use one field’s value;
• Template — compose a string from several values;
• Conditional — apply only when a DSL condition matches (empty condition means always).

Condition and template syntax is documented in the expression language reference.

The results are presentation-cache values used everywhere a record is shown compactly: lists, lookups, reference labels, cards, dashboards, and reports. Until a display name rule matches, records fall back to their record number.

Do not confuse these with Display fields, which are additional read-time values for table and card surfaces.

Statements

Statements are named boolean conditions defined on the entity Schema tab. Each statement is a reusable predicate over the record’s data (for example, “is overdue” or “needs review”).

Screens and rules reuse statements consistently: they appear as Data Explorer filters, drive grid and card highlighting, and keep the meaning of a business condition in one place instead of re-writing the expression on every surface. The statement expression syntax is documented in the expression language reference.

Where to go next

• Display fields for computed labels on tables and cards.
• Logic overview for validation and mutation logic.
• Business logic when the topic becomes authoring and diagnostics.