Start with a Report or a Flow
Start in Report Workbench when your work begins with written values, tables, and an explanation. Start in PXFLOW Studio or the Python SDK when the calculation structure comes first. A Flow can run on its own, and a Report can connect its authored values to that Flow whenever you want the Result placed in the document.
Choose where to start
Core names on screen
| Name | Start with this meaning |
|---|---|
| Project | A workspace that holds Reports, Flows, installed Component packages, and Results |
| Report | A document that stores its body, authored values and tables, Flow connections, and result positions |
| Report Workbench | The screen for writing a Report and connecting Flow inputs and results |
| Flow | An executable calculation arranged as Nodes and connections in PXFLOW |
| Function | A reusable calculation capability shared across Flows |
| Component | A capability selected from Components and placed in a Flow |
| Component package | The install and release unit that can provide one or more Components |
| Node | One calculation, input, transformation, or Component step placed in the current Flow |
| Run | One execution record created from a saved Flow revision and its inputs |
| Result | The values and evidence saved by a Run |
Connect a Report and a Flow
In Report Workbench, open @ Insert → PXFLOW, choose a Project and Flow, then choose the direction. Send a Report-authored value or table to a public Flow input, or place a public Flow result at the selected Report position. The Report saves both mappings while the Flow keeps its own Nodes and internal connections.
- Start writing in Report Workbench
- Connect Report values and Flow results
- Map scalar, Record, and Table inputs
- Understand the SDK and PXFLOW Studio boundary
Extend a Flow with Components
Current production guidance covers built-in and first-party Nodes only. Production third-party Exact ProjectScope data-path isolation is implemented. Component install admission and third-party Component activation remain blocked until Project authorization and the execution-trust closure are implemented and proven end to end; the current Flow reader keeps the exact target as a read-only unsupported diagnostic.
The V2 projection is host-owned component.declarative@2, with settings declared through component-declared-settings@1. Package-owned renderer code does not enter the Canvas; any richer surface belongs to component-rich-surface-declaration@1, the RFC-016 successor. These contracts do not make third-party installation or placement available today.
Use the Python SDK when you need code ownership
Use the Python SDK to author or automate a Flow, a Report, or both. It also supports reusable Functions and Components. PXFLOW Studio and Report Workbench open the same .pxflow and .pxreport documents produced by the SDK.