Create a Filterer configuration
A Filterer Configuration saves the Rules that decide which Records are kept in the output and which Records are removed during a Run.
Filterer does not change values in the dataset. It applies Record-selection logic to the File or dataset you run, then produces a focused output from the Records that should stay in scope.
Before you begin
Make sure you have:
- an Import Config for the File format you want to filter
- a clear name for the Filterer Configuration
- a clear decision about which Records should be kept or removed
- the Fields you want to use for filtering
- examples of Records that should be kept and Records that should be removed
Filterer uses the selected Import Config to show the Fields available for Rules. If the selected Import Config has no current revision, has no enabled Fields, or uses a type that is not supported for Filterer Field selection, the page shows a warning.
Typical workflow
A practical way to build a Filterer Configuration is:
- Open Filterer and go to Filterer Configurations.
- Select Create New Config or + New Filter.
- Enter a Filter name.
- Choose an Import configuration.
- Decide what should happen When no rule matches a row.
- Go to Build Rules and select Add rule.
- Choose the Column, Condition, Value, and Then action for each Rule.
- Review the Rule preview and the order of your Rules.
- Go to Review and Save, add an optional Description and Output base name, and choose a Status.
- Select Save draft or Save Filter Config.
When you edit an existing Configuration, the page uses tabs named Data, Rules, and Settings. Use Save to save a new revision of the Configuration.
Screen overview
The Filterer create screen is organized into three tabs.
| Area | What it is for |
|---|---|
| Choose Data | Name the Configuration, choose the Import Config, and set the default behavior for Records that do not match any Rule. |
| Build Rules | Add, order, enable, disable, and configure Rules. |
| Review and Save | Review the selected data source, enabled Rules, default behavior, expected result labels, status, description, and output name. |
The edit screen uses a more compact layout:
| Area | What it is for |
|---|---|
| Data | Choose or change the Import Config. |
| Rules | Set default behavior and edit the Rule list. |
| Settings | Edit Status, Description, and Output Base Name. |
| History | Opens the Configuration history for the saved Configuration. |
Fields and settings
| Field or setting | What it means | Notes |
|---|---|---|
| Filter name or Config Name: | The name users see when choosing the Configuration. | Required. Use a name that describes the business purpose. |
| Import configuration or Import Config | The import setup that defines which Fields are available for Rules. | Required. Changing it refreshes the available Field list. |
| When no rule matches a row | The default behavior for Records that do not match any enabled Rule. | Choose Keep the row or Remove the row. |
| Status | Whether the Configuration is saved as a draft, published, or archived. | Use the status that matches your team's review process. |
| Description | Optional business context for the Configuration. | Maximum length shown in the UI is 400 characters. |
| Output base name or Output Base Name | Optional name stored with the Configuration for output naming. | If blank, the runner generates a timestamped name. |
Default behavior
The default behavior applies only when no enabled Rule matches a Record.
| Option | What it means | When to use it |
|---|---|---|
| Keep the row | Records stay in the output unless a matching Rule removes them. | Use this when you mostly want the input dataset to stay intact and only remove specific Records. |
| Remove the row | Records are removed unless a matching Rule keeps them. | Use this when the Rules define the allowed Records for the output. |
For example, if your goal is "keep only active customers," set the default behavior to Remove the row and add a Rule that keeps Records where the status Field means active.
Rules
Rules run from top to bottom. The first enabled Rule that matches a Record decides whether that Record is kept or removed. If no enabled Rule matches, Filterer uses the default behavior.
Each Rule includes these main controls:
| Control | What it means |
|---|---|
| Add rule | Adds a new Rule to the Configuration. |
| Use this rule | Turns the selected Rule on or off without deleting it. Disabled Rules are ignored during a Run. |
| Move rule up and Move rule down | Change the order in which Rules run. |
| Delete rule | Removes the selected Rule. |
| Rule name | Optional name that explains why the Rule exists. |
| Column | The Field to evaluate. The list comes from the selected Import Config. |
| Condition | The comparison Filterer applies to the selected Field. |
| Value | The value used by the condition, when the condition needs one. |
| Then | What happens when the Rule matches: Keep the row or Remove the row. |
| Case sensitive | Controls whether text matching treats uppercase and lowercase as different. |
| Rule preview | Shows a sentence describing how the selected Rule will behave. |
The Case sensitive switch is available for text-style comparisons. It is disabled for numeric comparison conditions.
Rule options
Filterer currently shows these Condition options.
| Condition | What it checks | Value required? |
|---|---|---|
| is exactly (=) | The Field value equals the entered value. | Yes |
| is not (!=) | The Field value does not equal the entered value. | Yes |
| is greater than (>) | The Field value is greater than the entered number. | Yes |
| is at least (>=) | The Field value is greater than or equal to the entered number. | Yes |
| is less than (<) | The Field value is less than the entered number. | Yes |
| is at most (<=) | The Field value is less than or equal to the entered number. | Yes |
| contains (text) | The Field value contains the entered text. | Yes |
| starts with (text)* | The Field value starts with the entered text. | Yes |
| *ends with (text) | The Field value ends with the entered text. | Yes |
| is blank (= blank) | The Field is blank. | No |
| is not blank (!= blank) | The Field is not blank. | No |
| is one of (in) | The Field value matches one of several entered values. | Yes |
For is one of (in), enter comma-separated values such as Active, Pending. Filterer trims extra whitespace around each value.
Validation and warnings
Filterer blocks saving when required setup is missing. Confirm these items before saving:
- Filter name is filled in.
- An Import configuration or Import Config is selected.
- Each enabled Rule has a Column selected.
- Each enabled Rule has a Value when its Condition requires one.
You may also see warnings if the selected Import Config cannot provide Fields for the Rule editor. For example, Filterer may warn when the selected Import Config has no current revision or no enabled Fields.
Previewing rules before saving
The editor includes Rule preview, which restates the selected Rule in plain language. Use it to confirm that the Rule says what you intend.
Filterer screens do not show a full output preview before saving. For a new or changed Configuration, run Filterer on a small representative File first, then review the output before using it downstream.
Common mistakes to avoid
Avoid these patterns:
- setting the default behavior to Keep the row when your goal is to keep only a narrow allowed subset
- setting the default behavior to Remove the row without adding a Rule that keeps the Records you need
- relying on a Field whose values are inconsistent, blank, or not maintained well
- putting a broad Rule above a more specific Rule that should have decided the Record first
- leaving an old Rule enabled after the business rule changes
- reusing a Configuration with a File whose Field names do not match the selected Import Config
After the Configuration is ready
Once the Configuration is saved and tested, continue to Run Filterer to apply it to a File or dataset and review the result.