When creating filters inServiceNow, the elements should be specified in the following order:
Field– The database field (column) that is being filtered.
Operator– The comparison method, such as "is", "contains", "greater than", etc.
Value– The specific data that the filter should match.
Example of a Properly Structured Filter:Imagine filtering a list ofIncidentswhere the priority is high. The filter would be structured as:
Field:Priority
Operator:is
Value:High
is– Matches an exact value
is not– Excludes a specific value
contains– Looks for a partial match
greater than– Finds records with a value greater than the specified one
less than– Finds records with a value less than the specified one
B. Field, Operator, then Condition– Incorrect.
"Condition" is not an individual filter element in ServiceNow; theoperatoralready defines the condition (e.g., "is", "contains").
C. Operator, Condition, then Value– Incorrect.
The field must comefirstto define what data is being filtered. The operator follows next.
D. Value, Operator, then Field– Incorrect.
This is completely reversed; you must specifywhat fieldyou are filtering first before applying conditions.
ServiceNow Product Documentation → Filters and Condition Builder
ServiceNow CSA Study Guide → Data Management and List Filters
ServiceNow List Views → Using Filters and Operators
Common Operators in ServiceNow Filters:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:
Submit