anchor.diff:  |Collection
   a|Specifies whether the JSON expansion of a String payload should be done. If no content found or in case of parsing error, the content is kept "as is". +
    +
  -Fore more details, please see the xref:expanding-escaped-json-string-as-json[expanding escaped json] section.
  +Fore more details, please see the xref:mongodb-outbox-expanding-escaped-json-string-as-json[expanding escaped json] section.
   
   |[[mongodb-outbox-event-router-property-collection-fields-additional-placement]]<<mongodb-outbox-event-router-property-collection-fields-additional-placement, `collection.fields.additional.placement`>>
   |
  
positive.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-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:
  
negative.code: 
  // Type: concept
  // Title: Expanding escaped JSON String as JSON
  // ModuleID: mongodb-outbox-expanding-escaped-json-string-as-json
  [[mongodb-outbox-expanding-escaped-json-string-as-json]]
  == Expanding escaped JSON string as JSON
  
  By default, the `payload` of the {prodname} outbox message is represented as a string.
  When the original source of the string is in JSON format, the resulting Kafka message uses escape sequences to represent the string, as shown in the following example:
  
  [source,javascript,indent=0]
  ----
  