Configuring Strategy Parameters in FMZ
Summary
This guide explains how FMZ strategy interface parameters are defined and used in code. It covers numeric, Boolean, string, dropdown, and encrypted string values, including how language support differs. For example, Python functions need a global declaration to modify a global parameter, while PINE strategies create inputs through a dedicated function. The document also explains that parameter names should avoid reserved words and that optional, unset values vary by type.
It describes component choices such as sliders, time pickers, and selectors, plus grouping and conditional filters that control when parameters are available. It also outlines saving backtest settings in strategy code and exporting or importing live-trading parameters. These are platform configuration features, not trading signals or evidence of strategy performance. The guide does not discuss how to choose parameter values, validate a strategy, or manage the trading risks that may result from configuration choices.
Key ideas
- Strategy interface values are available to supported strategy languages as global variables, with language-specific rules for modifying them.
- Optional unset parameters can produce empty strings or empty values depending on their type.
- Component configuration supports different input controls, parameter groups, and conditions that determine availability.
- Backtest settings can be embedded in strategy configuration, while live parameters can be exported and imported.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.