Map Report values and tables to Flow inputs
An authored Report value is the source; a public Flow input is the destination. One source can be reused across several destinations, while each destination input has one active source. All input mappings added to one connection travel together as one Flow Run's input set.
Create the input region and binding together
At an empty caret, type @ and confirm Connect input in the Resolver. That one confirmation creates the editable input region and Flow input binding together. You can also start from selected ordinary text or a number; the selection initializes the new input but remains ordinary Report content until confirmation. A blank required input is connected but incomplete and becomes ready to run only after its value is committed.
When several named values belong to one structured value and appear at separate positions in a sentence or list, confirm @ once at each visible position. Connections made this way belong to the same structured value, so they are stored together as one mapping. Esc, Cancel, or the guide's Exit before confirmation creates neither object at that position. An earlier position already confirmed in the same action remains connected. Undo or Disconnect removes both in one edit and unwraps the value as ordinary Report content. Surrounding prose, lists, and tables stay unchanged.
A permanent load G and a variable load Q that belong to one structured value follow this sequence separately. Confirm @ at each position, create a blank connected input, and type its value; the two connections are then stored together as one mapping.
Choose the value shape first
| Report source | Public Flow input | What to review |
|---|---|---|
24.0 m, 42 | number | Numeric type, unit, and scalar shape |
S355 | text | Text type and allowed values |
true | boolean | Boolean type |
| A named set of fields | Record | Field mapping and each field's type and unit |
| Several items | List<T> | Item source and item type |
| Rows and fields with a stable key | Table<Record> | Row key and column mapping |
| Report attachment or Project resource | artifact | Artifact kind and access |
Results use the same value shapes. Number, text, and boolean results can appear inline; Record, List, and Table results can appear by field or in result blocks; artifacts use dedicated artifact positions.
Connect one number, text, or boolean
- For a new value, place the caret at an empty position. To use existing content as the initial value, select its text, number, or boolean.
- Type
@or open @ Insert → PXFLOW. - Choose the Project and Flow, then Use report input.
- Select a public input with a compatible type and unit.
- In Review connection, confirm the new input for the empty position or the selected source value, together with the destination input.
- Choose Connect input.
At an empty caret, the final Connect input confirmation creates the empty editable field and input mapping together. The selected-value path creates the field and mapping at the same step.
Map Record, List, and Table fields explicitly
For a structured value, pair each Report field with the Flow field it feeds. That pairing is the field mapping, and it — not the visible column order — defines the connection, so reordering or adding columns on screen leaves existing connections intact.
Map one Record
A Record is a named field set that describes one item.
| Report field | Flow section Record field |
|---|---|
section_width | width |
section_depth | depth |
steel_grade | grade |
- Select the Report fields that form one Record.
- Choose a Record input such as
section. - Under Connection, select a destination field for each Report field.
- Review required fields, types, units, and nullability, then choose Connect input.
Map one List
List<T> is one collection whose items share a type.
- For
List<number>, map each value from a selected Report field as one item. - For
List<Record>, choose a stable item source and the Record field mappings. - In Review connection, confirm the item count, item type, and order.
For example, mapping three rows from a factor field to List<number> sends [1.0, 1.35, 1.5] as one collection value in one Run.
Map one Table
A Table holds several rows of the same shape. Connecting one means setting two things.
- Row key: the value that identifies each row. In the example below,
case_idis the row key. Rows are matched by this value instead of by row number, so sorting the table or inserting and deleting rows keeps each row's input and result together. Choose a column whose values never repeat. - Field mapping: which Flow Table column each Report column feeds.
Using @ to promote an existing ordinary table range into a connected input is planned. Today, Connection → Table mapping only edits an already connected table's fields and row keys. To create a new connected table, type @ at an empty paragraph caret, choose the Table input, and confirm Connect input; that confirmation creates the table region and binding together.
| Report field | Flow load_cases Table field | Role |
|---|---|---|
case_id | case_key | Stable row key |
permanent | permanent_g | number [kN] |
variable | variable_q | number [kN] |
- At an empty paragraph caret, type
@, choose the Table input, and confirm Connect input. - Enter the rows and fields, including the stable row key and every field needed by the calculation.
- Open the saved connection and go to Connection → Table mapping.
- Set the row key and each destination field.
- Review types, units, required fields, and the selected row count.
- Apply the mapping to the current draft and Save the Report.
Connected cells and rows show a compact @ mark together with a direction label:
- Report → Flow sends a Report range to a Flow input.
- Flow → Report displays a Flow result at a Report position.
- Selecting the
@mark reopens that mapping in the resolver. - Turning off Connections hides the marks without removing content or mappings.
Map a Table result into the Report just as explicitly. For example, map the result's case_key, utilization, and passed fields to the Report's case_id, ratio, and status fields. The stable row key aligns each result row with its original case.
Map one artifact
Select a Report attachment or Project resource, then choose a compatible artifact input. In Review connection, confirm the artifact kind, source name, and access. The Run receives an authorized resource reference, preserving the same provenance from Report through Result.
Reuse sources and resolve destination conflicts
Reusing one Report source across different inputs creates a separate mapping for each destination. For example, span = 24.0 m can supply both clear_span and analysis_length. Editing the source marks both mappings and their affected Results Stale.
If two Report sources target one Flow input, the editor shows Duplicate destination. Choose the one source that should own the input; the other mappings remain unchanged.
Choose one collection Run or one Batch with child Runs
Choose by the destination shape, not by how many rows are selected.
| Goal | Destination | Run count | Result state |
|---|---|---|---|
| Calculate several values as one collection | List<T> | 1 | The complete list belongs to one Result |
| Calculate several Record rows as one table | Table<Record> | 1 | A Table result can include stable row keys and row statuses |
| Calculate each row as an independent scalar case | Scalar input set in an explicit Batch Run | One child Run per case | Every stable case key has its own Run state and Result |
Run one collection
| Report selection | Public Flow input | Value sent |
|---|---|---|
| One cell | Scalar | One scalar |
| N rows × one field | List<T> | One list |
| N rows × several fields | Table<Record> | One typed table |
| Several fields for one item | Record | One named field set |
When the Flow needs row-level outcomes, expose a Table result with the stable row key, status, calculated values, and diagnostic fields. Report Workbench displays the Table as one Run's Result, so successful rows and rows needing review share the same provenance.
Run several scalar cases as a Batch
- Select the rows that supply the scalar input sets.
- Choose Create Batch Run from the shape guidance.
- Review the stable case key and complete input set for each row.
- Review inputs shared by every case and inputs that vary by case.
- Confirm the case count and result destination, then choose Run batch.
For example, ULS-01, ULS-02, and SLS-01 create three child Runs. They can execute in bounded parallel when capacity is available, and completion order is unspecified. The Batch view shows Queued, Running, Succeeded, Failed, or Cancelled for each stable case key and its Result.
When some cases succeed and others fail, the Batch summary reports the partial status. Completed Results remain available; select only the necessary child Runs to Retry or Cancel.
Keep input and result fields in the same table
One table can send authored fields as inputs and display calculated fields as results.
| Case | Permanent G | Variable Q | Utilization | Status |
|---|---|---|---|---|
| ULS-01 | authored value | authored value | Flow result | Flow result |
| ULS-02 | authored value | authored value | Flow result | Flow result |
| SLS-01 | authored value | authored value | Flow result | Flow result |
- The Report document owns authored input fields;
px.Reportand Report Workbench edit them. - Result fields display an immutable Result as read-only content.
- The
case_keymapping connects input rows, result rows, and provenance. - After editing an input or the Flow, choose Run again to project the new Result into the result fields.
The selected ranges stay visible while the resolver lists the compatible typed result fields.
Edit a mapping
- Turn on Connections.
- Select the
@mark on the value or table range. - In the resolver, change the source, Flow, or public input.
- For a Record, List, or Table, review the field mappings again.
- Confirm the updated route in the row direction labels and the summary below the table.
- Apply the draft change and Save the Report.
Immediately after creation, Undo removes the input region and binding together. For a saved connection, Disconnect does the same and leaves the value as ordinary Report content.
Resolve type, unit, and shape states
| State | Meaning | Next action |
|---|---|---|
| Compatible | Source and public-input contract match | Connect or Apply |
| Shape mismatch | Scalar and collection shapes differ | Choose a collection input or create a Batch Run |
| Unit mismatch | Unit conversion needs review | Choose a compatible input or confirm an explicit conversion |
| Missing required input | The same Run needs another input mapping | Add the listed source mapping |
| Missing field | A required Record or Table field has no source | Map a source field to the destination field |
| Duplicate destination | Two sources target one public Flow input | Choose one source |
| Stale result | An input, mapping, or Flow changed after the Run | Save and Run again |
Understand the saved mapping
The Report stores stable semantic keys for the selected block, table, rows, and fields rather than screen coordinates. It also stores the Project, exact Flow revision, public input, and connection Run policy. The Flow continues to own its Nodes and internal connections.
See the Report-to-PXFLOW input mapping contract for the exact .pxreport source fields and input and result types and units for Record, List, and Table rules.