---
id: SCH-31
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-31
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# SCH-31 — Config field order applies inside a ui schema only

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

## The rule

> **Normative.** This is the rule.
>
> 1. `x-config-order` orders config fields ascending; a property whose value is absent or not numeric counts as 0, and ties keep declaration order.
>
> 2. It takes effect inside a generated ui schema only: where no property carries a registered group there is no ui schema, no layout, and `x-config-order` has no effect on the flat form.
>
> 3. The earlier spelling `x-display-order` carries no meaning; a schema that still writes only it orders at 0, like any untagged property.

## Related rules

- Names: SCH-23
- Referenced by: SCH-4, SCH-23

---

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.