Skip to main content

When to use Filterer

Choose Filterer when you already have the Records you need in the dataset, but you only want some of them in the output.

That usually means your next step depends on a repeatable inclusion or exclusion decision.

Strong signs that Filterer is the right Tool​

Filterer is a strong fit when:

  • you need only part of a larger File or dataset
  • you want a repeatable Rule for inclusion or exclusion
  • you are preparing a smaller subset for export, review, upload, or another WebHammers step
  • the main question is "which Records belong?" rather than "how should the values be fixed?"

Typical business situations​

Filterer is commonly used in situations like these.

Keep a targeted subset​

Examples:

  • only active accounts
  • only open cases
  • only Records within a reporting period
  • only Records from one business unit, site, or region

Remove Records that should not continue downstream​

Examples:

  • test or training Records
  • cancelled or closed transactions
  • Records outside a policy date range
  • Records from categories that are out of scope for the process

Build a review queue​

Examples:

  • Records needing human follow-up
  • Records with a high-priority status
  • exceptions that should be handed to another team
  • a narrow group of Records for review or sampling

Good fit vs. poor fit​

Good fit​

Use Filterer when the answer can be described as:

  • "Keep Records that meet these conditions."
  • "Remove Records that match these conditions."
  • "Separate the Records that belong to this business scenario."

Poor fit​

Filterer is probably not the first Tool to use when the real problem is:

  • values need to be cleaned or standardized first
  • duplicate Records must be identified and resolved
  • Fields need to be validated against business rules
  • Fields need to be restructured, mapped, renamed, or transformed before selection logic will work reliably

Ask this before you start​

A simple test is to finish this sentence:

"From this File, I need the Records that ..."

Examples:

  • "From this File, I need the Records that are still active as of month-end."
  • "From this File, I need the Records that should be excluded from the external export."
  • "From this File, I need the Records that require manual review."

If you cannot describe the target Records clearly yet, clarify the business Rule before building the Configuration.

Start with a narrow goal​

For a first Configuration, start with one focused outcome instead of a broad all-purpose setup.

Better:

  • "Keep only currently open invoices for Region East."

Riskier:

  • "Handle every invoice scenario the team might ever need."

Narrow Configurations are easier to test, explain, reuse, and update.

Start with a representative sample​

Before running on a full dataset, test on a small sample that includes:

  • Records that should definitely stay
  • Records that should definitely be removed
  • boundary cases
  • blanks or unusual values if those occur in real data

This helps confirm that the Configuration reflects the actual business intent before you use it at scale.

Questions that indicate you should use another Tool first​

Pause and consider another Tool if you find yourself asking questions like:

  • "These values are inconsistent. Should I standardize them first?"
  • "I do not trust the formatting in the source File."
  • "I need to detect duplicates before deciding which Records to keep."
  • "I need to confirm validity before I choose the subset."
  • "I need to remove, rename, or reorder Fields in the output."

If the answer is yes, handle that earlier step first, then return to Filterer once the selection logic is reliable.

Rule-of-thumb decision guide​

Use Filterer when the central task is Record selection.

Use a different Tool first when the central task is cleaning, deduplicating, validating, mapping, or restructuring.