---
id: SCH-23
family: GR-SCHEMA
level: extended
profiles: [storage-api, editor-client]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/gr-schema/sch-23
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# SCH-23 — When a node has a ui schema, and when it has none

*GR-SCHEMA (Part I) · level: extended · profiles: storage-api, editor-client · added in 1.0*

The ui schema is what turns a flat config form into grouped sections. Whether there is one at all is decided by a single question about the final schema.

## The rule

> **Normative.** This is the rule.
>
> 1. The ui schema is generated from the final config schema, after every reserved property has been injected.
>
> 2. It is null exactly when no property carries a registered group: a property tagged with an unregistered group falls into the default bucket, so a schema tagged only with unregistered groups also yields null, and the form stays on its flat path.
>
> 3. Groups are collapsed by default; a group is opened for a node instance where that instance sets one of the fields in it.

## Related rules

- Names: SCH-21, SCH-31
- Referenced by: SCH-31

---

Rule identifiers are permanent and are never renumbered. This specification carries
no implementation status: each implementation publishes its own standing against
these rules. Licensed CC BY 4.0.