Splitter examples
These examples show the kinds of business problems Splitter can help solve.
Example 1: Split cases by region
A case export contains records from several regions. Each regional team needs only its own records.
Use Splitter to create separate outputs for each region.
Why Splitter fits
The source is one file, but the desired result is several group-specific outputs.
Example 2: Separate approved, rejected, and review records
A vendor File includes an approval status Field with approved, rejected, and needs-review values.
Use Splitter to create separate outputs for each status.
Why Splitter fits
Records need to be routed into multiple destinations based on a repeatable Field value.
Example 3: Route invoice exceptions away from standard records
An invoice file contains standard records and records that require follow-up because of missing values, unusual amounts, or policy exceptions.
Use Splitter to send standard records to one output and exception records to another.
Why Splitter fits
The workflow needs more than one output, and exception records should not be mixed into the standard file.
Example 4: Create separate upload files
One operational File feeds multiple downstream systems, and each system accepts a different subset of Records.
Use Splitter to produce the upload files from one source.
Why Splitter fits
The task is recurring file routing with clear destination rules.
Example 5: Isolate uncategorized records
A dataset should divide cleanly by category, but some records contain blank or unexpected categories.
Use Splitter to create normal category outputs plus an uncategorized review output.
Why Splitter fits
Splitter can expose records that do not fit expected routing logic so they can be corrected or reviewed.
Practical pattern
For each Splitter use case, define:
- the input file
- the output groups
- the routing Fields
- the rule for each group
- the fallback or exception handling
If those pieces are clear, you are usually ready to build a Splitter configuration.