Table of contents
- Introduction
- General description
- The different parts of the Value-remover Transformer
Introduction
When working on a request with big data, sometimes there is a need to remove values from the data. In the past, it was complicated to unset values. For this, you might need to use the “Value mapper” transformer and add mappers with values you would like to remove.
Now it is possible to solve such a tricky issue with the “Value remover” transformer which is used to remove values from the requests or anything that accepts transformers.
Follow the path: Connections → Entity transformers → Create an entity transformer to see how the “Value remover” works.
General description
The Value-remover Transformer can be used to remove unnecessary entity data from an incoming request. This could be for privacy reasons or simply because System A delivers more data than needed in System B.
The different parts of the Value-remover Transformer
-
Patterns (required)
At least one pattern is required. A pattern functions as a filter that is applied to the keys in the context data to determine whether an element needs to be removed or not. -
Key (required)
This specifies a key in the entity data that needs to be removed. The field supports placeholders and JMESPath expressions.
