Filter condition anatomy

Also seen as: filter, filter chip, filter rule

What are the three parts of a filter condition?

Every condition answers the same question in three pieces — which metric, tested how, against what.

The metric comes from the filter taxonomy — 118 filters grouped into three categories and 20 subcategories. The operator comes from the filter's own operator list: see standard operators for the comparison set, and special relations for the pattern tests such as crossings that a handful of filters offer instead. The wider shapes a comparison can take — a fixed number, a range, the metric's own earlier reading, a rank, or a market or sector figure — are covered in comparison modes.

What does the "You're saying" line show?

You're saying is the filter editor's plain-language restatement of the condition you have just built, rewritten live as you change the operator or the value. It reads the three parts back as one sentence — "ROE is greater than 15%." — so you can check the rule says what you meant before you apply it. Until you have picked values it reads "Choose values to see what this filter says."

The sentence uses words where the dropdown uses glyphs: < reads "is less than", ≤ reads "is at most", = reads "equals", ≥ reads "is at least", and > reads "is greater than".

Defaults in Fincanva

• A filter arrives with the operator and value its catalogue entry declares, so a condition is valid the moment you add it — the ROE filter opens at > 20%.
• Values snap to the stops that filter offers. You can type a number freely; on Enter, or when the field loses focus, it moves to the nearest stop.
• Each filter offers only the operators and comparison modes it supports; the editor hides the rest rather than showing them disabled.
• Conditions combine with AND and run in the order they sit in the filter strip — see sequential filtering and Top-N ranking.
• The optional Advanced panel adds Lag, Period, and Multiplier, which shift or scale the reading before the comparison; see lag, period, and multiplier.
• The chip is the same condition in compact form: the filter name, then any non-default Advanced settings as (period) [lag], then the operator and the value.
• The count of instruments still passing every condition is the match count.

Worked example: building "ROE > 15%"

Four moves, each one touching a single part of the condition.

1. Add the filter. Open Add filter. The flyout has three columns — Category, Subcategory, Filter. Pick Fundamental, then Profitability, then ROE. The condition arrives at its catalogue default, ROE > 20%.
2. Check the operator. The operator dropdown groups its choices under Compare, Range, and Rank. > — labelled "greater than" — is already selected under Compare, so there is nothing to change.
3. Set the value. Type 15 in the value field. The ROE filter's stops run in one-point steps, so 15 lands exactly on a stop and the field shows 15%.
4. Read it back. You're saying now shows "ROE is greater than 15%." Apply, and the chip in the strip reads ROE > 15%.

The condition now keeps every instrument whose most recent return on equity reads above 15% and drops the rest. Because > is strict, an instrument sitting at exactly 15% does not pass; switching the operator to ≥ ("at least") includes the boundary.