Users of Sift Workflows sometimes want to build policies on text fields. This includes criteria like:
- Block all email addresses of the form firstname.lastname@example.org
- Approve all IPs that are of the form 10.*.*.*
- Block listings that contain ‘Disney’ or ‘disney’
- Review all orders where the item name contains ‘gift card’
To enable building criteria of this form, we have Advanced Text Matching options:
- Partial vs whole word matching → For any new criteria you set up on text fields, Sift Workflows will match on whole words by default. This means that a filter for ‘text me’ will not trigger on ‘text megan’. However, you can force an override to match on substrings (ie partial words) via the Substring Match checkbox. Something is a substring if it exists anywhere in the string, no matter what's to the left or right of it. So, if you check the "Substring Match" box, then ‘car‘ would match ‘A car for sale‘, ‘card‘, ‘email@example.com‘, etc. If you do not check "Substring Match", we'll only find ‘car‘ if it's not bordered by a non-letter, non-number character, including the start or end of the string. So, ‘car‘ would match ‘car.‘, ‘free-car‘, ‘I have a car for sale‘, ‘firstname.lastname@example.org‘, etc, but not ‘card‘, ‘5car4‘, or ‘I have a carforssale‘.
- Case sensitivity → By default, Sift will ignore case on text fields. So ‘email@example.com’ will trigger on ‘email me at JohnDoe123@gmail.com’. This may be overridden by checking the "Case Sensitive" checkbox.
- Wildcards → We also have support for wildcards. The two wildcards we support are ‘*’ (for 0-many characters) and ‘%’ (for 0-1 character). For example, ‘firstname.lastname@example.org’ will trigger on ‘email@example.com’, ‘firstname.lastname@example.org’, ‘email@example.com‘, etc. ‘free bitcoin%%‘ will trigger on ‘free bitcoins!‘, ‘free bitcoins‘, and 'free bitcoin', etc.
Please reach out to firstname.lastname@example.org if you have any questions.