Search vs Studio Differences
Although SFHub expression has commonality with all web applications and services, some of the operators and operands are supported in Studio only. In addition, there are significant differences between Studio analytic and the other web applications.
Variables
Variables can only be used in Studio expressions.
Attribute notation
In principle, referencing attributes in Studio is simpler than in a generic search expression. Studio offers integrated Switch/Case features. Also, Studio Analytic logic is applied toward each element of the workspace, thus strong notation is less important in Studio.
Table access
Table can be accessed using the facilitated notation using the Search.
Examples
[material] = 'crude'
Search engine will look for table column which name is material. Notice that the column name is not enclosed in single quotes although it's a string.
["material"] = 'crude'
Search engine will look for table column which name is the value of the attribute material. Notice that the column name is enclosed in quotes.
Studio does not support facilitated notation and therefore:
[material] = 'crude'
Studio will look for table column which name is the value of the attribute [material].
['material'] = 'crude'
Search engine will look for table column which name is [material].
Notice that the column name is enclosed in single quotes to indicate that it's a string literal.
Using strong notation in search expression
The use of attribute strong notation has removed the need for additional tokens.
Examples
Meter Abs(Test1) > 5
The result will be all elements matching the [Meter] token (element name or template name or category name) and whose attribute [Test1] absolute value is greater than 5.
Abs(SF_GasMeterTemplate:o_Rec_Test1) > 5
The result will be [equal]. The attribute strong notation filters out elements by template name, producing the same result as the previous expression.