CreateImpositionSpecInput
Input for creating a component or batch form imposition specification
Fields
Exclusive BatchComponent owner; omit componentId
Typed whole-signature carrier arrangement for a batch form; source geometry and identities are reused
Exclusive Component owner; omit batchComponentId
External system identifier, unique per integration. Written to the calling integration's own identity; the creating integration's identifier stays primary.
HTTP(S) link to this specification in the external system; requires an external identity. Explicit null clears it, omission keeps it.
Name for this imposition scenario
Description of this imposition scenario
Mark as the primary/selected imposition plan (defaults to false)
Pages per sheet (up-count)
Sheets required per form run
Total number of form runs
Total page count
Sheet-work scheme
Possible values (5)
WORK_AND_TURNWork-and-turn (both sides from same plate, sheet flipped on long edge)
WORK_AND_TUMBLEWork-and-tumble (both sides from same plate, sheet flipped on short edge)
SHEETWISESheetwise / work-and-back (separate plates for each side)
WEB_PERFECTWeb perfecting (both sides printed inline)
OTHEROther scheme
Page orientation for planning
Possible values (3)
PORTRAITPortrait orientation
LANDSCAPELandscape orientation
BEST_FITBest-fit (automatic orientation selection)
How the section is bound. Supply it for anything that folds — page order on a signature depends on it, and without it the sheet is imposed sequentially.
Possible values (7)
SADDLE_STITCHSaddle stitch: all sheets nest inside each other
PERFECT_BOUNDPerfect binding: gathered signatures glued at spine
CASE_BOUNDCase binding: sewn or glued signatures in hard cover
WIRE_BOUNDWire binding: pages bound with wire spiral or comb
FLATWORKFlatwork: no binding, step-and-repeat
FOLDEDSingle fold, no gathering or binding
OTHEROther or unspecified binding method
Horizontal gutter between up-positions; each LengthInput carries its own unit.
Vertical gutter between up-positions.
Sort order (defaults to 0)
Sheet geometry authored outside CoCoCo, stored with layoutStatus IMPORTED instead of being synthesized from pagesUp/scheme/orientation; later edits to those fields keep it. Component specifications only; a plan-qualified signature or a batch form refuses it.
Referenced by (1)
Exact type SDL
"""Input for creating a component or batch form imposition specification"""
input CreateImpositionSpecInput {
"""Exclusive BatchComponent owner; omit componentId"""
batchComponentId: BatchComponentID
"""
Typed whole-signature carrier arrangement for a batch form; source geometry and identities are reused
"""
batchLayout: BatchFormLayoutInput
"""Exclusive Component owner; omit batchComponentId"""
componentId: ComponentID
"""
External system identifier, unique per integration. Written to the calling integration's own identity; the creating integration's identifier stays primary.
"""
externalId: String
"""
HTTP(S) link to this specification in the external system; requires an external identity. Explicit null clears it, omission keeps it.
"""
externalUrl: String
"""Name for this imposition scenario"""
name: String
"""Description of this imposition scenario"""
description: String
"""Mark as the primary/selected imposition plan (defaults to false)"""
isPrimary: Boolean
"""Pages per sheet (up-count)"""
pagesUp: Int
"""Sheets required per form run"""
sheetsPerForm: Int
"""Total number of form runs"""
totalForms: Int
"""Total page count"""
totalPages: Int
"""Sheet-work scheme"""
scheme: ImpositionScheme
"""Page orientation for planning"""
orientation: ImpositionOrientation
"""
How the section is bound. Supply it for anything that folds — page order on a signature depends on it, and without it the sheet is imposed sequentially.
"""
bindingType: BindingType
"""
Horizontal gutter between up-positions; each `LengthInput` carries its own unit.
"""
gutterH: LengthInput
"""Vertical gutter between up-positions."""
gutterV: LengthInput
"""Sort order (defaults to 0)"""
sortOrder: Int
"""
Sheet geometry authored outside CoCoCo, stored with layoutStatus IMPORTED instead of being synthesized from pagesUp/scheme/orientation; later edits to those fields keep it. Component specifications only; a plan-qualified signature or a batch form refuses it.
"""
layout: LayoutScalar
}