managedDocumentProfileV1

This reference describes the full structure of managedDocumentProfileV1. 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
contract	"DocumentProfile@1"	Required. Exact discriminant of this contract variant. Match the literal value shown.
key	string; min length 1	Required. Stable semantic identifier used by references; changing it changes identity.
sourceSurfaceDefinitionPaths	Array<string; min length 1; semantic validation>	Required. Exact path of the relevant definition type; each reference must exist in the Model and respect declared scope.
template	"article" | "report" | "manuscript" | "project-brief"	Required. Defines template for this object. Observe the type, variants and bounds in the Options column.
sectionPolicy	"ordered" | "grouped"	Required. Defines section Policy for this object. Observe the type, variants and bounds in the Options column.
exportFormats	Array<"docx" | "markdown" | "pdf">	Required. Defines export Formats for this object. Observe the type, variants and bounds in the Options column.

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.

{
  "contract": "DocumentProfile@1",
  "exportFormats": [
    "pdf",
    "markdown"
  ],
  "key": "account-preference-documents",
  "sectionPolicy": "ordered",
  "sourceSurfaceDefinitionPaths": [
    "workspace/account-home/surface/preferences/surface/preference"
  ],
  "template": "report"
}

Related references

Complete Model index · Build a Model

Applied examples : Client notes and exported document

Content stays editable in the record; the export profile selects the authorized quotes.

Configuration

Contract object managedDocumentProfileV1. Properties and accepted values.

{
  "contract": "DocumentProfile@1",
  "exportFormats": [
    "pdf",
    "markdown"
  ],
  "key": "account-preference-documents",
  "sectionPolicy": "ordered",
  "sourceSurfaceDefinitionPaths": [
    "workspace/account-home/surface/preferences/surface/preference"
  ],
  "template": "report"
}

Variation and connection

Fragment placed in documentProfiles[]. Properties and accepted values.

{
  "contract": "DocumentProfile@3",
  "key": "client-quotes-export",
  "source": {
    "kind": "record-query",
    "recordProfileKey": "client",
    "queryBindingKey": "client-quotes",
    "viewKey": "quotes-table"
  },
  "exportFormats": [
    "markdown"
  ],
  "budget": {
    "maximumRows": 100,
    "maximumPages": 4,
    "maximumOutputBytes": 1000000
  }
}

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. Quote S-1042
2. Subject and need
3. Proposal
4. Retained references

SurfaceClients / North StudioExample

managedDocumentProfileV1managedDocumentProfileV1

Clients

MODEL CONTEXTNorth StudioDeclarative configuration

exportFormats

2 items

key

account-preference-documents

sectionPolicy

ordered

sourceSurfaceDefinitionPaths

1 item

template

report

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