Strategy

Simple Strategies

Simple strategies use flat key-value parameters configured via dynamically generated form fields. When creating a strategy via Create Strategy definition, you select the strategy type under Strategy name in the dialog Strategy definition, and the system automatically displays the appropriate input fields. Only the types permitted on the selected level, and not already present there in a unique form, are offered. When editing, only the parameters can be changed, not the strategy type. Simple strategies include price alerts, indicator alerts and portfolio rebalancing.

Complex Strategies

Complex strategies have a nested configuration. When a complex strategy is selected, a YAML editor with syntax highlighting, autocompletion, continuous syntax checking and explanations when hovering over a key appears instead of dynamic form fields. A new strategy is pre-filled with a template; Load Template restores it at any time. The checkbox Active appears for complex strategies only: when it is switched off, even an incomplete draft can be saved, which is not evaluated. Apply saves the strategy.

See Editing and validating YAML for the shared controls. Validate takes the Active setting into account: an inactive draft may remain incomplete, but any YAML text entered must be syntactically valid. An active strategy must also meet the requirements for an executable configuration. Apply validates again; errors leave the text in the dialog for correction.

Strategy Types Overview

graph TD
    S["Strategy Types"] --> R["Rebalancing"]
    S --> P["Price Alerts"]
    S --> I["Indicator Alerts"]
    S --> K["Complex Strategies"]
    R --> R1["Portfolio Rebalancing"]
    P --> P1["Absolute price gain/lose"]
    P --> P2["Holdings gain/lose"]
    P --> P3["Gain/loss in a period"]
    I --> I1["Moving average crossing"]
    I --> I2["RSI threshold"]
    I --> I3["Custom expression"]
    K --> K1["Mean Reversion Dip"]

The following table lists all available strategy types with their assignment levels. The level indicates whether the strategy can be assigned to the portfolio based strategy, to an asset class or to a security. The column Effect states what the strategy brings about in the portfolio monitoring of your own portfolio and in a simulation. Alerts are not evaluated in a simulation because they know neither the direction nor the quantity of an order; the reasoning is given under Where each strategy takes effect. Portfolio rebalancing and the Mean Reversion Dip can be entered only once per node, all other types several times.