In a config modifier schema, use pipe to stack the outcome of a previous keyword as the input of the next. The keywords need to exist at the same nesting level for the keywords to be evaluated in order.
Think of this like a math equation with a parenthetical statement that must be resolved before calculating. For example, 2 + 4 x 6 would have a different outcome from 2 + (4 x 6). In this way, the pipe keyword allows you to bracket keywords for a particular order of operations within the overall schema.
Exclusive keywords
This keyword executes at the following nesting level:
- omit
- constant
- references
- use
- get
- properties or if or concat or switch or pipe or merge
- default
- plugin
You can change VisitDateTime to ISO format.
Example: Pipe input from initial payload
json
Example: Pipe selector
json
Example: Config modifier with pipe keyword
yaml
Based on this example config modifier schema, VisitDateTime is updated to ISO format.
Example: Pipe output in processed payload
json