Typing an area, device, function, DB number, or address fragment in the result search box uses contains matching. A row enters the current view when the symbolic address, DB number, absolute address, or offset field contains that text.
Typing an area, device, function, DB number, or address fragment in the result search box uses contains matching. A row enters the current view when the symbolic address, DB number, absolute address, or offset field contains that text.
When the search text contains %, % means any number of characters. Expressions can match multiple ordered fragments or constrain both prefix and suffix. In real projects, use the site's standard area code, device code, function name, or signal suffix.
Keep-name, exclude-name, alarm-name, and trend-name rules in Rule Center use the same matching rules. Multiple rules can be separated by new lines, commas ,, or semicolons ;. Plain words use contains matching. Without %, *, or ?, the rule is not an exact match; for example, PUMP means the same as *PUMP*.
% and * mean the same thing: any number of characters, including zero characters. ? means exactly one arbitrary character. When a wildcard is written, boundary position matters. For example, PUMP% starts with PUMP, %PUMP ends with PUMP, and %PUMP% contains PUMP.
Rules primarily match normalized fields such as symbolic address, DB name, source path, comment, table name, address, and data type. Name-based rules are intended to narrow results by naming fragments. Wildcard expressions can match ordered area, device, function, or signal fragments from the site's naming standard.
Start with a broad keep rule to define the main scope, then use exclude rules for backup, history, and temporary objects. Prefer stable naming fragments instead of short incidental text.
