Flow Editor — Overview

The Flow Editor is the heart of QANode. It is where you create, configure, and run your test scenarios visually.

Editor Interface

The editor is divided into four main areas:

Image: Flow editor showing the four areas: top bar, node palette, canvas, and properties panel

1. Top Bar

The top bar contains:

2. Node Palette (Left Side)

The palette displays all available nodes organized by category:

• Flow Control — If, Switch, Loop
• Web — Smart Web Flow, Web Flow, Smart Locators
• Mobile — Mobile Flow
• API — HTTP Request
• Database — PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB
• Files — Generate File, Extract File, Base64 to File, File to Base64
• Infrastructure — SSH Command
• Performance — Load Test
• Utilities — Set Variable, Log, Wait, Stop and Fail, Custom JavaScript
• Custom Nodes — Nodes from registered providers (if any)

To add a node, drag it from the palette to the canvas.

3. Canvas (Central Area)

The canvas is the workspace where you position and connect nodes. Features:

4. Properties Panel (Right Side)

When you select a node, the properties panel appears on the right with:

• Run: Executes the node in isolated mode
• Variables: Opens the properties of previous nodes, local variables, global variables, and, when applicable, project variables
• Configuration: Fields specific to the node type
• Outputs: The node's output schema (after execution, shows the actual data)
• Continue on Failure: Toggle to continue the flow even if the node fails

Typical Workflow

1. Create the scenario from a project
2. Drag nodes from the palette to the canvas
3. Connect nodes by dragging between handles
4. Configure each node using the properties panel
5. Save the flow (Ctrl+S)
6. Run and check the results

Execution Order

QANode executes nodes in topological order, determined by the connections:

[A] → [B] → [D]
         ↘
[C] ──────→ [E]

In this example:

• A executes first
• B and C can execute next (after A)
• D executes after B
• E executes after B and C

Note: If a node has multiple inputs, it only executes when all previous nodes have completed.

Visual Indicators

After a run, nodes display status indicators:

Keyboard Shortcuts

Canvas Annotations

Annotations help document parts of the flow directly on the canvas. Use them to explain preconditions, business rules, logical groups, pending work, or notes for the team.

Annotations support:

• free text;
• simple Markdown-style formatting;
• colors;
• resizing;
• dragging and positioning on the canvas;
• copy, paste, duplicate, and delete.

You can create an annotation from the canvas context menu or with Shift+A.

Unsaved Changes

The editor automatically detects when there are unsaved changes. When you try to leave the page (via the back button, navigation, or closing the tab), a warning will be displayed:

"Leave without saving?" You have unsaved changes. If you leave, your changes will be lost.

This protects against accidental loss of work. The warning only appears when there are real changes — not when opening a flow without modifying it.

Version History — Enterprise

QANode Enterprise can keep scenario snapshots when relevant flow changes are saved. The history helps audit changes, compare versions, and return to an earlier version when needed.

To access:

1. Open the scenario in the editor.
2. Click the Version History icon in the top bar.
3. Select a version to view.

When you open an older version, the scenario is shown in read-only mode. You can navigate the canvas, select nodes, and inspect parameters, but you do not edit the snapshot directly.

To return to an earlier version, use Restore this version. QANode applies that snapshot as the current scenario version and preserves traceability of the operation.

Version history is available only in Enterprise. The number of retained versions is defined by the Super Admin in Settings → General.

Next Steps

• Working with Nodes — Details on adding, connecting, and configuring nodes
• Execution and Debugging — How to run flows and diagnose failures