Skip to main content

Data fields

The Data pane has tabs: Fields (with Test Data), Lists (repeating lists), Actions (custom actions), Connections, and Schema (what playout sees). Counts show what each holds.

Data fields​

Use Data → Fields to edit field definitions and values. Data → Operator controls provides a searchable tree of the current template's controls, grouped by scene objects with nested object properties and array items. Each control shows its OGraf exposure status and a checkbox deciding whether it appears in the exported graphic's public data schema and accepts external playout updates. Exposure is enabled by default, including for existing templates. Uncheck it to keep a field internal: its default value, bindings, Rules, animations and Studio controls remain available. Required applies only when the field is exposed.

Object and group checkboxes change all their controls together. Checked means all are exposed, unchecked means none are exposed, and a mixed checkbox means only some are exposed; clicking a mixed checkbox exposes all. These bulk changes include collapsed or filtered-out controls and recursively update their object properties and array items.

The tree distinguishes a control's own checkbox from its effective status. An internal parent field keeps its children internal without changing their individual choices; an internal item schema keeps the whole array internal. Generated shader fields appear in the same tree; hiding one from playout does not remove its shader control or animation. Exposure choices are saved in .ogs and respected by standalone and coordinated exports. An explicit template-level exposure choice is preserved when its field inherits a shared control's value. When states in a coordinated lane expose different fields, their forms use conditional schemas. Controllers that resolve these conditions show the selected state's fields; the package also enforces the exposure policy when receiving external data.

Public updates to part of an object preserve its internal values, including nested branches left out of the update. Exported schemas, public defaults and data examples include only exposed fields; the graphic retains internal defaults for its own Rules and animation after loading or replaying.