workspaceRecordCalculationSource
Properties, variants, types and bounds for workspaceRecordCalculationSource.
This reference describes the full structure of workspaceRecordCalculationSource. 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 |
"calculation" |
Required. Selects the variant and the properties admitted in this branch. |
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": "calculation",
"calculationKey": "client"
}
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 workspaceRecordCalculationSource. Properties and accepted values.
{
"kind": "calculation",
"calculationKey": "client"
}
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.
- Client identity
- Notes and follow-up
- Settings
- Linked quotes
kind- calculation
calculationKey- client
Values above follow the configuration fragment; references resolve in the complete Model.