A Strong Performer in The Forrester Wave™: Digital Experience Platforms, Q4 2025
Contentstack
Changelog

Operand Fields and Supported Operators

When configuring field-based operations, it is essential to understand the available fields and their corresponding supported operators. The table below outlines various field types and the specific operators that can be applied to each field.

Field NameSupported Operators
Title
  • Matches
  • Does not match
  • Starts with
  • Ends with
  • Contains
URL
  • Matches
  • Does not match
  • Starts with
  • Ends with
  • Contains
Single Line Textbox
  • Matches
  • Does not match
  • Starts with
  • Ends with
  • Contains
Multi Line Textbox
  • Matches
  • Does not match
  • Starts with
  • Ends with
  • Contains
Select
  • Is
  • Is not
Number
  • Equals
  • Not equals
  • Less than
  • Less than or equals
  • Greater than
  • Greater than or equals
Boolean
  • Is
  • Is not
Date
  • Is
  • Is not
  • Before
  • After
Reference
  • Is
  • Is not
Note:
  • The Matches and Does not match operators are case sensitive.
  • You cannot use the Rich-Text Editor, JSON Rich Text Editor, Markdown, File, Link, Custom, Taxonomy fields as the operand fields.

  • When a Group field is marked as Single, you can use the parent and its sub-fields as operands. When marked as Multiple, you cannot use the parent group field itself, but you can use its sub-fields as operands.

  • For Modular Blocks, neither the parent block nor nested child blocks can be used as operands. You can only select its sub-fields from within the same block as operands.

More articles in "Field Visibility Rules"