anchor.diff:  [[mongodb-outbox-event-router-configuration-options]]
   == Configuration options
   
  -The following table describes the options that you can specify for the outbox event router SMT. In the table, the *Group* column indicates a  configuration option classification for Kafka.
  +The following table describes the options that you can specify for the outbox event router SMT.
  +In the table, the *Group* column indicates a configuration option classification for Kafka.
   
   .Descriptions of outbox event router SMT configuration options
   [cols="30%a,20%a,10%a,40%a",options="header"]
  
positive.code: 
  The second value is the placement and it must always be `header` or `envelope`.
  
  Configuration examples are in xref: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`>>
  |
  
negative.code: }
  ----
  
  This example of a {prodname} outbox message is based on the xref:mongodb-outbox-event-router-configuration-options[default outbox event router configuration], which assumes an outbox collection structure and event routing based on aggregates.
  To customize behavior, the outbox event router SMT provides numerous xref:mongodb-outbox-event-router-configuration-options[configuration options].
  
  // Type: concept
  // Title: Outbox collection structure expected by {prodname} mongodb outbox event router SMT
  // ModuleID: outbox-collection-structure-expected-by-debezium-mongodb-outbox-event-router-smt
  [[basic-mongodb-outbox-collection]]
  == Basic outbox collection
  
  To apply the default MongoDB outbox event router SMT configuration, your outbox collection is assumed to have the following fields:
  