Skip to content
SurfaceDocs
FRGet started
DocsModel reference

SurfaceWorkExperience · types

Interfaces, values and named contracts for SurfaceWorkExperience.

The following types define named objects and their relationships. Tables include inherited properties. Schema-derived types refer to their validated structures; a TypeScript declaration does not replace the compiler’s semantic checks.

SurfaceWorkScope

One context resolved by the native Work reader under its retained execution Model.

export type SurfaceWorkScope = z.infer<typeof surfaceWorkScopeSchema>;

SurfaceWorkHeaderValue

Scalar declaration only; source values remain with their native read owner.

export type SurfaceWorkHeaderValue = z.infer<typeof surfaceWorkHeaderValueSchema>;

SurfaceWorkHeaderFact

Labelled scalar fact, not a computed or materialized Field.

export type SurfaceWorkHeaderFact = z.infer<typeof surfaceWorkHeaderFactSchema>;

SurfaceWorkHeader

Explicit header slots belonging to the same Work programme.

export type SurfaceWorkHeader = z.infer<typeof surfaceWorkHeaderSchema>;

SurfaceWorkExperience

Native declaration, without runtime node identities, grants, SQL, scripts or renderer addresses.

export type SurfaceWorkExperience = z.infer<typeof surfaceWorkExperienceSchema>;

SurfaceWorkQueryBinding

One declared Query invocation; its scope supplies canonical values under the same watermark.

export type SurfaceWorkQueryBinding = z.infer<typeof surfaceWorkQueryBindingSchema>;

SurfaceWorkBinding

One named capability selected only through its section’s explicit membership.

export type SurfaceWorkBinding = z.infer<typeof surfaceWorkBindingSchema>;

All references

Applied examples : Compose a record and its relations

Two declared Stacks hold main content then relations without extra frames. The preset selects the right panel’s width.

Configuration

Component properties RecordLayout.props. Properties and accepted values.

{
  "asideWidth": "standard"
}

Variation and connection

Component properties RecordLayout.props. Properties and accepted values.

{
  "asideWidth": "compact"
}

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
ILLUSTRATIVE LAYOUTClients / Quotes app
SurfaceClients / North StudioExample
SurfaceWorkExperience · typesCompose a record and its relations
Clients
NS
North StudioActive client · Professional services
StatusActive
Notes and follow-up

The client wants a proposal for a new project. Clarify requirements and confirm the budget before review.

Editable text on the Surface
Record settings
Search for a concept, field or action.Esc