workspaceRecordValueSource

This reference describes the full structure of workspaceRecordValueSource. 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
[kind=native].kind	"native"	Required. Selects the variant and the properties admitted in this branch.
[kind=native].property	"title" | "description" | "createdAt" | "updatedAt"	Required. Recognized native property name; this selector does not allow arbitrary access.
[kind=field].kind	"field"	Required. Selects the variant and the properties admitted in this branch.
[kind=field].fieldPath	string; min length 8; max length 127; /^fields\/[a-zA-Z][a-zA-Z0-9]*$/u	Required. Semantic Field selector, using the fields/ prefix.
[kind=calculation].kind	"calculation"	Required. Selects the variant and the properties admitted in this branch.
[kind=calculation].calculationKey	string; min length 1; max length 120; /^[a-z][a-z0-9-]*$/u	Required. Stable key reference to the corresponding named declaration; the compiler checks existence and compatibility.

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.

{
  "kind": "field",
  "fieldPath": "fields/name"
}

Related references

Complete Model index · Build a Model

Applied examples : Visible notes, accessible settings

Place follow-up on the Surface and email in settings, while retaining the same Fields.

Configuration

Contract object workspaceRecordValueSource. Properties and accepted values.

{
  "kind": "field",
  "fieldPath": "fields/name"
}

Variation and connection

Fragment placed in presentation.recordProfiles[].detail.settings. Properties and accepted values.

{
  "fieldPaths": [
    "fields/email"
  ]
}

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

workspaceRecordValueSourceworkspaceRecordValueSource

Clients

MODEL CONTEXTNorth StudioDeclarative configuration

kind

field

fieldPath

fields/name

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