Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor guides
  4. /Use the Inspector
BeginnerLast verified Sep 30, 2026

Use the Inspector

Configure the current selection and understand its parameters, outcomes, data ports, and quick actions.

On this page
  1. Prerequisites
  2. Inspect a node
  3. Inspect other selections
  4. Work on compact screens

The Inspector changes with the current selection.

Prerequisites

Sign in to an account with Flow Editor access and open a strategy. Editing Inspector values requires permission to edit the strategy; historical previews remain read-only.

Inspect a node

Select a node to see:

  • Parameters for saved configuration.
  • Outcomes for possible control branches.
  • Data Ports for typed inputs and outputs active in the current configuration.
  • Quick actions for the selected node when they are allowed.

Use the help action beside an unfamiliar item. A connected-node action can move focus to a related node.

In the RSI Starter, select Condition and compare the three tabs. Parameters says what comparison to make: Greater than, a connected Left value, and a literal Right value. Outcomes shows the possible Match and No Match control branches. Data Ports shows the active numeric input used by the connected Indicator. A port is a place for a typed value; an outcome is where execution continues. Treating one as the other produces an invalid connection.

Changing a parameter can change the active ports. For example, switching Condition's Right source from Literal to a connected data port requires a compatible Right input. After the switch, review the edge and the validation area before saving. The node reference lists definitions; the Inspector shows the current node instance.

Try it here

Inspect the signal

Select different nodes and inspect their parameters, outcomes and data ports.

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.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

Inspect other selections

Select a connection to inspect its source, destination, and kind. Select the canvas to see graph-level context. A multiple selection exposes actions that apply to the group.

When a branch behaves unexpectedly, select its control connection and confirm the source outcome first. Then select the data connection that supplies the condition and confirm source port, destination port, and data type. This separates “the rule evaluated to No Match” from “the rule never received a value.” If an Inspector action is disabled, read its stated permission, plan or mode requirement before changing the graph.

Work on compact screens

On a compact viewport, the Inspector opens as an overlay and may close another workspace drawer. Close it with its visible action or Escape, then confirm that focus returns to a useful control.

Historical preview is read-only. Full replay uses the Replay Dock instead of the Inspector.

Related documentation

  • Configure a nodeEdit required and optional parameters, then review any ports or connections affected by the change.
  • Nodes, parameters, outcomes, and portsRead the parts of a node and understand what to configure or connect.
  • Manage variablesDeclare, read, update, rename, and remove Flow variables while preserving their references.

On this page

1 / 4
  1. Prerequisites
  2. Inspect a node
  3. Inspect other selections
  4. Work on compact screens

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary