Use the Engineering Paper Component
Planned Extension UI
This page describes a contract-only Engineering Paper editor journey. The production Flow reader currently opens the exact Component target as a read-only unsupported Node and preserves raw settings plus usage-derived partial ports. It has no settings schema, Open editor action, or document-projection bridge. Host presentation belongs to the contract_only V2 in Node presentation and third-party UI.
Engineering Paper is the target Component for an optional document-authoring Extension.
Planned Canvas and editor surface
The target Canvas contains one Engineering Paper Node. Its planned editor contains Sections, Formula blocks, Evidence tables, and mapped values as document elements.
Connect values
Use ordinary result-to-input bindings on the Canvas. In the planned editor, choose Mapped value to place a current Node input into a document block. The current Flow owns execution and the editor owns the document projection.
Save and artifacts
| Item | Created by |
|---|---|
| Document draft | Editor Save; stored in the Flow revision's Node setting |
| Document artifact | the Engineering Paper Component during the saved Flow Run; returned through its named result port |
| PDF artifact | explicit Export PDF from a Document artifact |
These Component artifacts are separate from the .pxreport document authored with px.Report or Report Workbench.
Optional Component SDK
The planned @px.paper API registers a reusable template definition. Import the Component package's companion @px.component definition and place it with flow.node(..., paper_components.engineering_paper, ...). Select the template through the raw Component setting; a versioned settings schema and editor are not implemented. The Flow owns Node placement and connections.