managedExactDataValueType

This reference describes the full structure of managedExactDataValueType. Paths include nested objects, list items and conditional branches. A branch selected by kind, contract or mode only admits its own properties.

Structure and values

Field	Options / expected values	Description
format	closed object; semantic validation	Required. Presentation format compatible with the value type.
format.precision	integer; ≥ 1; ≤ 1000	Required. Defines precision for this object. Observe the type, variants and bounds in the Options column.
format.scale	integer; ≥ 0; ≤ 1000	Required. Defines scale for this object. Observe the type, variants and bounds in the Options column.
unit	closed object OR closed object OR closed object	Required. Defines unit for this object. Observe the type, variants and bounds in the Options column.
unit.[kind=dimensionless].kind	"dimensionless"	Required. Selects the variant and the properties admitted in this branch.
unit.[kind=unit].kind	"unit"	Required. Selects the variant and the properties admitted in this branch.
unit.[kind=unit].key	string; min length 1; max length 120; /^[a-z][a-z0-9-]*$/u	Required. Stable semantic identifier used by references; changing it changes identity.
unit.[kind=currency].kind	"currency"	Required. Selects the variant and the properties admitted in this branch.
unit.[kind=currency].key	string; min length 1; max length 120; /^[a-z][a-z0-9-]*$/u	Required. Stable semantic identifier used by references; changing it changes identity.

Reading the contract

A path ending in [] describes each list item; {key} describes each dictionary value. The ↻ marker refers to the same recursive expression. Closed objects reject additional properties. Semantic validation denotes an additional check: matching a type does not make a reference, permission or transition valid. References must resolve in the Model and the current user context.

An older variant cannot accept properties belonging to a newer variant. The compiler checks the version and consistency of the complete Model.

Structural example

This fragment passes the schema for this section. Its business references must be defined in the enclosing Model.

{
  "format": {
    "precision": 1,
    "scale": 0
  },
  "unit": {
    "kind": "dimensionless"
  }
}

Related references

Complete Model index · Build a Model

Applied examples : Required text and business choices

Company uses required text input; Status uses a declared list of choices.

Configuration

Contract object managedExactDataValueType. Properties and accepted values.

{
  "format": {
    "precision": 1,
    "scale": 0
  },
  "unit": {
    "kind": "dimensionless"
  }
}

Variation and connection

Fragment placed in forms[].fields[]. Properties and accepted values.

{
  "contract": "WorkspaceFormControl@2",
  "repeatable": false,
  "key": "status",
  "label": "Status",
  "input": "choice",
  "binding": {
    "kind": "field",
    "fieldKey": "status"
  },
  "required": true,
  "ruleKeys": [],
  "options": [
    "prospect",
    "active"
  ]
}

UI layout example

The illustrative layout below places this configuration in the Clients/Quotes app. Insert each fragment at the stated location, with Field, Query and Action references matching the Model declarations.

1. Client identity
2. Notes and follow-up
3. Settings
4. Linked quotes

SurfaceClients / North StudioExample

managedExactDataValueTypemanagedExactDataValueType

Clients

MODEL CONTEXTNorth StudioDeclarative configuration

format

Declared object

unit

Declared object

Values above follow the configuration fragment; references resolve in the complete Model.