anchor.diff:  |Becomes the Kafka message key, which is important for keeping ordering within Kafka partitions
   
   |`type`
  -|The `type` column becomes part of the message envelope as `eventType`
  +|The `type` column becomes either part of the message envelope as `eventType` or message header. +
  +See option `table.fields.additional.placement` for more details.
   
   |`payload`
  -|The JSON representation of the event itself, becomes part of the message as `payload`
  +|The JSON representation of the event itself, becomes either part of the message as `payload` or if other metadata including `eventType` are delivered as headers then the payload becomes the message itself without an encapsulation in an envelope
   |=======================
   
   
  
positive.code: |`table.fields.additional.placement`
  |
  |Table, Envelope
  |Extra fields can be added as part of the event envelope or a message header; the format is a list of colon-delimited pairs or trios when you desire to have aliases, e.g. `id:header,field_name:envelope:alias`. Placement options are `header` and `envelope`
  
  |`table.field.event.schema.version`
  |
  
negative.code: |The default regex to use within the RegexRouter, the default capture will allow to replace the routed field into a new topic name defined in `route.topic.replacement`
  
  |`route.topic.replacement`
  |`outbox.event{zwsp}.${routedByValue}`
  |Router
  |The name of the topic in which the events will be routed, a replacement `${routedByValue}` is available which is the value of The column configured via `route.by.field`
  
  