TR-GAB DocsBack to TR-GAB
Workflows

Turn a trading idea into a repeatable pipeline.

Workflows connect mining, backtesting, validation and broker export in one ordered process. Build the flow once, run it again when the market, symbol or test window changes, and keep every result organized in databanks.

Build visually Add, reorder, enable or pause processes without rebuilding the whole pipeline.

Move candidates through databanks Route each process from an input bank to the same bank or a different output bank.

Finish on the target platform Export and test through the tools available for MetaTrader 5, NinjaTrader, cTrader and LEAN.

TR-GAB Workflows with an ordered strategy pipeline and its workflow databank

A real workflow captured automatically from the current development version of TR-GAB.

The model

Every workflow has three parts:

  1. Processes define what happens and in which order.
  2. Databanks hold the candidates read or produced by those processes.
  3. Runs preserve the execution state and the strategies produced by the pipeline.

Each process selects an input databank and an output databank. Choose same as input for an in-place step, or send the result to another databank to preserve stages such as raw candidates, filtered candidates and validated candidates.

Generate→Backtest→Filter→Validate→Export

Build and organize

Use the left sidebar to create workflows and organize them into lists and groups. A workflow can be marked as a favorite, renamed or cloned. Lists, groups and workflows can be reordered, compacted and expanded as the library grows.

The main toolbar provides the actions used most often:

  • Rename and Clone the selected workflow.
  • Compact All or Expand All to control dense pipelines.
  • Board to inspect workflow results in the visual board.
  • Run to execute every enabled process in order, or Cancel an active run.
  • Use the platform action to export the workflow through the current default broker.
  • Create an MT5 snapshot when a separate copy of the current Expert workspace is required.

Cloning a workflow copies its process configuration and databank structure, but not its strategy items. Workflow templates can also be imported or exported as .trgwf: they include groups, lists, workflows, process settings and databanks, never the generated strategies.

Process catalog

Generate candidates

Miner · RuleSearches entries built from price, indicators and logical conditions.
Miner · PatternFinds recurring price structures using pattern similarity.
Miner · EventBuilds candidates around selected economic-calendar events and time windows.

The miners share the strategy inputs that matter across the product: source data, symbol, timeframe, date mode, execution precision, costs, money management, account limits, trade limits, trading windows, exits and output filters.

Test and validate

BacktestRe-runs candidates with their stored configuration or with selected overrides and recalculates KPIs.
Simple RetesterTests the same strategies on a different symbol, timeframe, date range or precision without rebuilding them.
FilterKeeps or removes candidates using reusable KPI clauses.
Robustness FilterRuns controlled perturbations and Monte Carlo checks before accepting a candidate.
Walk-ForwardEvaluates rolling in-sample and out-of-sample windows and exposes the resulting matrix and detail.

Combine and improve

Backtest · CombinatorCombines candidates from selected databanks, applies limits and backtests the resulting strategies.
Backtest Combinator · Different SidesPairs BUY and SELL candidates, optionally restricted to the same symbol.
EvolverCreates parameter variants over generations and retains the strongest results.
Add ConditionAdds an extra entry condition and re-tests the affected strategies.

Export and test on a platform

MetaTrader 5Export MT5 and MT5 Tester Batch.
NinjaTraderExport NT and NT Tester Batch.
cTraderExport cTrader and cTrader Tester Batch.
LEANExport LEAN, LEAN Tester Batch and LEAN Account Batch.

Exporters create the native artifact for the selected platform. Tester processes have platform-specific configuration and results; they are not treated as interchangeable wrappers. The default broker controls the native destination used by workflow-level export actions.

Data and routing tools

  • Update Symbols refreshes selected symbols already present in Market Vault.
  • Loop repeats downstream work across configured symbol and timeframe passes.
  • Move to Databank copies or moves the current candidates to another workflow databank.
  • Clear empties the selected workflow databank.

Work with processes

Every process row exposes the same operating controls:

  • Drag to change its order.
  • Enable or disable it without deleting its configuration.
  • Choose input and output databanks.
  • Edit or open its full configuration.
  • Copy its configuration, clone it, move it up or down, delete it or run it individually.

Configuration screens reuse the same editors as the Labs where possible. This keeps strategy settings consistent when a candidate moves from a miner or Lab into an automated workflow.

Inspect the databank

The workflow databank is the live result table. Add databanks, switch between them, import strategies and compact the section without leaving the workflow.

For each candidate you can inspect:

  • Origin, name, symbol, timeframe and direction.
  • Trades, win rate, risk/reward, profit factor, drawdown and net profit.
  • Equity curve and validation checks.
  • Stored broker-test results when a tester process has run.

Rows can be sorted, selected in bulk, copied between databanks, renamed, opened in the appropriate Lab, added to a Board, exported, saved to the strategy library or deleted. Clean All is guarded by confirmation and clears the workflow databanks, not the strategy definitions stored elsewhere.

Run safely

Press Run to execute the enabled chain in process order. Progress is attached to the active run, so the UI can reconnect to long operations and show which process is currently running. Individual processes can also be launched with their row action when a full pipeline is unnecessary.

Start with separate databanks for raw, filtered and final candidates. It makes every stage inspectable, prevents accidental in-place replacement and makes failed runs much easier to diagnose.

A practical first workflow

  1. Add a Miner · Rule, Miner · Pattern or Miner · Event.
  2. Write raw candidates to a dedicated databank.
  3. Add Backtest or Simple Retester for the target range.
  4. Apply a Filter, then Robustness Filter and Walk-Forward.
  5. Route survivors to a final databank.
  6. Add the exporter and tester for the target platform.
  7. Run the pipeline, inspect its checks and save or export only the candidates you want.

This structure stays simple for one symbol and scales to multi-symbol research through Loop and explicit databank routing.