anchor.diff:  }
   ----
   
  -A {prodname} connector that is configured to apply the MongoDB outbox event router SMT generates the above message by transforming a {prodname} raw message like this:
  +A {prodname} connector that is configured to apply the MongoDB outbox event router SMT generates the preceding message by transforming a raw {prodname} change event message as in the following example:
   
   [source,javascript,indent=0,subs="attributes"]
   ----
  
positive.code: 
  The delegate `Converter` implementation is specified by the `delegate.converter.type` option.
  If any extra configuration options are needed by the converter, they can also be specified, such as the disablement of schemas shown above using `schemas.enable=false`.
  endif::community[]
  
  // Type: concept
  // Title: Emitting additional fields in {prodname} outbox messages
  // ModuleID: emitting-additional-fields-in-debezium-outbox-messages
  [[emitting-messages-with-additional-fields]]
  == Emitting messages with additional fields
  
  Your outbox collection might contain fields whose values you want to add to the emitted outbox messages. For example, consider an outbox collection that has a value of `purchase-order` in the `aggregatetype` field and another field, `eventType`, whose possible values are `order-created` and `order-shipped`.
  
negative.code: 
  The second value is the placement and it must always be `header` or `envelope`.
  
  Configuration examples are in xref:mongodb-outbox-emitting-messages-with-additional-fields[emitting additional fields in {prodname} outbox messages].
  
  |[[mongodb-outbox-event-router-property-collection-field-event-schema-version]]<<mongodb-outbox-event-router-property-collection-field-event-schema-version, `collection.field.event.schema.version`>>
  |
  