Skip to content

Strategy editor

A strategy in ALRADEX is a process diagram (BPMN): blocks joined by flows. The engine walks the diagram from the Start block, executes each block and passes its results on as variables.

  • Blocks (left panel) — the palette. Drag a block onto the diagram or click it to add it automatically. Search is available.
  • Diagram — the canvas. The mouse wheel zooms, Fit diagram shows it whole.
  • Properties (right panel) — settings of the selected block or flow.
  • Lint panel — the diagram is checked as you edit: errors and warnings point at the block.
Group Elements
Start / end Start, End
Logic Condition (gateway), Gateway (any conditions), Parallel gateway
Tasks User task
Timers Pause (timer)
Blocks the platform’s trading blocks — see Blocks
  • Condition (gateway) — takes the first outgoing flow whose condition is true, or the default flow.
  • Gateway (any conditions) — activates every flow whose condition is true; when merging, it waits for all active branches.
  • Parallel gateway — activates all flows at once, without conditions; when merging, it waits for every incoming flow.

A condition is set on a flow leaving the gateway: select the flow on the diagram and configure it in the properties panel. See Conditions.

Holds the branch for a set time (seconds, minutes, hours, days), then continues with the next block. Strategies are usually built as a loop: fetch candles → compute → decide → pause → back to candles.

Each block writes its result to a variable available to every block further down the flow. The result variable can be renamed in the block’s properties (Variable name for result).

Parameters set when a strategy is run are available as strategyParams.<name> — for example, strategyParams.symbol. This lets one diagram trade different symbols.

When creating a definition you can:

  • start from an empty diagram;
  • Copy an existing strategy — its diagram becomes the starting point;
  • Import XML — upload a BPMN file.

Under More actions the diagram can be opened as XML and edited by hand; changes are applied with Apply and return to the diagram.

Save creates a new version of the diagram and sends it for deployment. A diagram with errors can still be saved, but a backtest will not start until they are fixed. See Versions and deployment.