managedExactDecimalRounding
Properties, variants, types and bounds for managedExactDecimalRounding.
This reference describes the full structure of managedExactDecimalRounding. 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
"half-even" \| "half-up" \| "toward-zero" \| "away-from-zero" \| "floor" \| "ceiling"
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.
"half-even"
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 managedExactDecimalRounding. Properties and accepted values.
"half-even"
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.
- Client identity
- Notes and follow-up
- Settings
- Linked quotes
Value- half-even
Values above follow the configuration fragment; references resolve in the complete Model.