Filter and path rules in FlowMattic

Use filters to guarantee that operations are only carried out on the objects you choose. With filters, you can specify a certain criterion to reach the desired level of granularity.

For instance, you can configure a filter to only record emails with a particular topic line or just clients who make a particular product transaction. Therefore, the next action in your FlowMattic workflow is initiated when the data from your previous action steps including triggers satisfies the criteria of a filter. No more actions are taken if a filter stops an item.

A task that is not passed by a filter is not executed while the workflow execution. Only tasks that are passed by filter are executed..

Filter rule types

Different logical rules can be applied using filters. Only the type of data that is indicated in brackets can be used with conditions. Text, numeric, date/time, boolean, and generic are the five different categories of filter rules.

Examples

You can see which fields would satisfy a particular rule in this table. Each example’s Rule is the filter rule that we’ve specified, the Value is what we’re comparing it to, and the Examples are inputs from action or trigger responses that the filter is comparing.

Rule	Value	Examples that would pass	Examples that wouldn’t pass
(Text) Contains	Apples and bananas	Apples Apple Apples and bananas	Strawberries
(Text) Does not contain	Apples and bananas	Strawberries	Apple
(Text) Exactly matches	Apples	Apples	Apple (not plural) apple (not uppercase)
(Text) Does not exactly match	Apples	Apple Banana And more	Apples
(Text) Is in	Apples, bananas	Apples Bananas	Apple Banana Strawberries
(Text) Is not in	Apples, bananas	Strawberries Apple	Apples Bananas
(Text) Starts with	App	Apples Applesauce	Apricots Bananas
(Text) Does not start with	App	Apricots Bananas	Apples Applesauce
(Text) Ends with	s	Bananas Apple and bananas	Apple
(Text) Does not end with	s	Apple Banana	Apples Bananas
(Number) Greater than	10	11100	9-1
(Number) Less than	10	9-1	100
(Date/time) After	12/31/2018 1:00	01/01/2019 12/31/2018 01:01	12/31/2017
(Date/time) Before	12/31/2018 1:00	12/31/2017	01/01/2019
(Date/time) Equals	12/31/2018 1:00	12/31/2018 1:00	12/31/2019 12/31/2018 00:00
Exists	n/a	Apple 10 01/01/2019
Does not exist	n/a		Apple 10 01/01/2019

Text filters

Text filters only work with text data, so they won’t work with numbers or dates.

1. Contains: Verifies if a field contains a specific value. It is not case-sensitive.
2. Does not contain: Verifies if a field does not contain a specific value. It is not case-sensitive.
3. Exactly matches: Checks if a field matches a value precisely, letter-for-letter. It is case-sensitive.
4. Does not exactly match: Checks if a field does not match a value precisely, letter-for-letter. It is case-sensitive.
5. Is in: Determines if a field exists in a list of values. It is not case-sensitive.
6. Is not in: Determines if a field does not exist in a list of values. It is not case-sensitive.
7. Starts with: Validates if a field starts with a particular value. It is not case-sensitive.
8. Does not start with: Validates if a field does not start with a particular value. It is not case-sensitive.
9. Ends with: Verifies if a field ends with a specific value. It is not case-sensitive.
10. Does not end with: Verifies if a field does not end with a specific value. It is not case-sensitive.

Number filters

Number filters only work with numeric values, like 1 or 100. They do not work with written forms of numbers (one, two, one hundred) or dates.

11. Greater than: Checks if a numerical field is greater than a specific value.
12. Less than: Checks if a numerical field is less than a specific value.
13. Equal to: Checks if a field is equal to a specific value. This is case-sensitive for text fields and exact for numerical fields.
14. After (date/time): Checks if a date or time field occurs after a specific date or time.
15. Before: Checks if a date or time field occurs before a specific date or time.
16. Equal: Checks if a field is equal to a specific value. This is case-sensitive for text fields and exact for numerical fields.

Boolean filters

17. Is true (Boolean): Checks if a Boolean field is set to true.
18. Is false: Checks if a Boolean field is set to false.

Generic filters

19. Exists: Checks if a field has a value or is not empty.
20. Does not exist: Checks if a field does not have a value or is empty.

If you have a series of items like this:

Whether FlowMattic continues to pass the filter depends on whether you use positive or negative filter conditions.

Examples of positive filter conditions are “contains” and “starts with”.

Examples of negative filter conditions are “does not contain” and “does not start with”.

If all filter conditions are positive

If all conditions are positive, at least one line item must pass all filter conditions for FlowMattic to continue.

In the example below, one item satisfies both positive conditions, even though the other does not, so FlowMattic continues. 

If the filter condition is both positive and negative, or all negative

If negative conditions are included, all line items must pass all filter conditions for FlowMattic to continue.

In the example below, one or more line items did not meet the filter criteria, so FlowMattic will not continue.