Update a pane
Requires panes:manage permission.
Laminate auto-splitting: When a pane with laminateRole: "single" is updated with routing that includes a laminate station, and rawGlass.sheetsPerPane is greater than 1 (either from the update body or from the existing pane data), the endpoint automatically splits the pane into a laminate structure:
- The existing pane becomes the parent (
laminateRole: "parent") with routing set to post-lamination stations only - N sheet panes are created (
laminateRole: "sheet") with routing up to and including the laminate station, each starting at the first station - Parent and sheets are linked via
childPanes/parentPane - Response shape becomes
{ parent: Pane, sheets: Pane[] }
This is the typical flow: panes are created without routing at Order Release, then when routing is assigned during release, the laminate split happens automatically.
Order release side effect: When a pane’s order field is set and the pane was previously unlinked (order: null), the target order’s paneCount is automatically incremented and progressPercent is recalculated. This is the mechanism used to release a remake pane into an order — the remake pane is created with order: null during claim approval, then later assigned to the order via this endpoint, which keeps the order’s pane count accurate. A real-time order:updated event is emitted.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Resource ID
Body
111Station ObjectId
1pending, in_progress, awaiting_scan_out, completed, claimed, defected Array of Station ObjectIds
1What the customer wants done (e.g. Laminated, Tempered, Beveled)
Corner cutting specification
Acceptable dimension tolerance
Array of hole positions and dimensions
Array of notch positions and dimensions
Processing steps required (e.g. temper, laminate, assembly, cnc)
11single, parent, sheet 111