Nodes, parameters, outcomes, and ports

A node represents one source, transformation, decision, action, wait, or annotation in a strategy.

Read a node in this order: what starts it, which values it needs, which setting changes its behavior, and what it can produce. These are separate questions. Moving a node on the canvas changes the drawing, not the direction of execution. A line is an edge; its source and target handles decide whether it carries control or data.

Parameters

Parameters are saved settings such as a symbol, timeframe, comparison operator, or message. Select a node and use the Parameters tab in the Inspector to change them.

Some controls appear only after another parameter is selected. Complete required values before relying on validation.

For example, choose Right source = Literal on Condition to enter 60 in the node. The Right data port is then inactive. Choose the data-port source only when another node should supply the comparison value. The literal's effective value type follows the operator and, for equality, the selected literal type; a generic text field in a reference table is not a claim that 60 becomes text.

Try it here

Inspect the signal

Inspect a node’s parameters, outcomes and data ports using a small editable graph.

Exercise steps

1. Inspect Condition in the properties panel; change Literal Right to 60.
2. Compare Parameters, Outcomes and Data Ports. Select another node on the canvas to inspect it.

Start lesson

Outcomes

Outcomes describe the possible control results of a node. Condition exposes Match and No Match. Order exposes outcomes for successful and unsuccessful submission paths.

Use the Outcomes tab to understand what each branch means before connecting an action.

With Left = 58, 60, and 62, the operator > against 60 selects No Match, No Match, and Match respectively. Equality is false for strict greater-than. If Match goes to Alert and No Match has no outgoing edge, the first two arrivals end without an alert. An unused outcome may be intentional; read the validation severity before changing the graph.

Data ports

Data ports accept or produce typed values. A connection is available only when the source and target types are compatible. The Data Ports tab shows the active ports for the current configuration.

Changing a parameter can change which ports are visible. Review existing connections after a configuration change.

The node reference lists possible ports across supported configurations. It does not mean all those handles appear together. The active Inspector configuration is the source for what you can wire now. A required port is required when that port is active. A missing Right handle under Literal is expected; a missing Left value for a numeric comparison is not.

Node help

Open the help action beside a node, parameter, outcome, or port for a concise explanation. Use the full guide link when you need an example or troubleshooting.

Check your understanding

If Indicator.RSI is connected to Condition.Left but Event Trigger does not reach Condition, you have supplied data without a control arrival. If Event Trigger reaches Condition but Left is unconnected, you have a path without the value it needs. Connect nodes walks through both edges; Condition explains the configuration variants.