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
Section titled “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
Section titled “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.
Checking child rows and related records
Section titled “Checking child rows and related records”A Statement can check the rows of its record’s child tables. Security
Statements and Workflow activation preconditions can also check the records
that reference this record. In the expression editor, choose Collection
condition, pick
ANY (at least one item matches), ALL (every item matches) or EXISTS, and
select the collection. The editor inserts the frame and places the cursor inside
WHERE ( ). There, field suggestions belong to one item, such as one order line.
ALL is true for an empty collection, so add COUNT(...) > 0 AND when the
record must have items. Security Statements and Workflow activation
preconditions can also look into the items’ own collections and
their Board or Workflow status. See
Collections and related records for the rules and
examples.
An exposed Statement can also be the permanent filter of an Entity list page. Each page selects one Statement from its own Entity Definition and requires it to be true, in addition to any search or user filters. Use separate pages for different subsets without duplicating the record type. These page filters do not replace Security Statements or record permissions.
Where to go next
Section titled “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.