anchor.diff:   +
   To change the topic name, you can: +
   
  -* Set the `route.by.field` option to a different column.
  -* Set the `route.topic.regex` option to a different regular expression.
  +* Set the xref:outbox-event-router-property-route-by-field[`route.by.field`] option to a different column.
  +* Set the xref:outbox-event-router-property-route-topic-regex[route.topic.regex] option to a different regular expression.
   
   |[[outbox-event-router-property-route-tombstone-on-empty-payload]]<<outbox-event-router-property-route-tombstone-on-empty-payload, `route.tombstone.on.empty.payload`>>
   |`false`
  
positive.code: |[[outbox-event-router-property-route-topic-regex]]<<outbox-event-router-property-route-topic-regex, `route.topic.regex`>>
  |`(?<routedByValue>.*)`
  |Router
  |Specifies a regular expression that the outbox SMT applies in the RegexRouter to outbox table records. This regular expression is part of the setting of the `route.topic.replacement` SMT option. +
   +
  The default behavior is that the SMT replaces the default `pass:[${routedByValue}]` variable in the setting of the `route.topic.replacement` SMT option with the setting of the `route.by.field` outbox SMT option.
  
  |[[outbox-event-router-property-route-topic-replacement]]<<outbox-event-router-property-route-topic-replacement, `route.topic.replacement`>>
  |`outbox.event{zwsp}.pass:[${routedByValue}]`
  
negative.code: * `error` - The SMT logs an error and continues to the next outbox table record.
  * `fatal` - The SMT logs an error and the connector stops processing.
  
  All changes in an outbox table are expected to be `INSERT` operations. That is, an outbox table functions as a queue; updates to records in an outbox table are not allowed.
  The SMT automatically filters out `DELETE` operations on an outbox table.
  ifdef::community[]
  |[[outbox-event-router-property-tracing-span-context-field]]<<outbox-event-router-property-tracing-span-context-field, `tracing.span.context.field`>>
  |`tracingspancontext`
  