Flow inputs carry an origin hint, run or panel
The Inputs editor and the canvas label show it, and the run forms leave panel inputs out.
This commit is contained in:
@@ -47,8 +47,10 @@ The initial value seeds an unset live message. Later publications take over;
|
||||
changing the starting value does not overwrite a value already in state.
|
||||
Use **Publish this value now** in the input row to send it immediately.
|
||||
|
||||
The canvas draws flow inputs as labelled endpoints. Without a producer or
|
||||
declared input, a consuming node reports `unconnected_input`.
|
||||
The canvas draws flow inputs as labelled endpoints, marked `run` or `panel`
|
||||
by what writes them. A panel input is one a dashboard or panel control writes,
|
||||
and the run form does not ask for it. Without a producer or declared input, a
|
||||
consuming node reports `unconnected_input`.
|
||||
|
||||
A batch flow's inputs are run parameters. Its **Result** section selects the
|
||||
messages returned when the run finishes. See [Runs](runs.md).
|
||||
|
||||
Reference in New Issue
Block a user