Evaluate the message against a rule or validation condition.
Message Transformation
Content Filter
Remove unneeded fields or simplify structure so downstream consumers receive only the data they require.
How do you simplify dealing with a large message, when you are interested only in a few data items?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Content Filter works
A rule decides whether a message continues through the normal flow or is removed from it.
Candidate message
Content Filter
Accepted
Ignored / isolated
Apply Content Filter to separate useful messages from unwanted or invalid ones.
Forward accepted messages and explicitly handle the rejected path.
What this pattern helps you decide
Remove unneeded fields or simplify structure so downstream consumers receive only the data they require.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- APIM set-body projection
- Liquid/JOLT transformation
- BizTalk map
How the analyzers can surface it
- Payload reduction transformations
- Field-level mappings
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.