anchor.diff:  </route>
   ----
   
  -[[OnCompletion-onCompletionwithglobalscope]]
  -== onCompletion with global scope
  -
  -This works just like the route scope except from the fact that they are
  +=== onCompletion with global level
  +
  +This works just like the route level except from the fact that they are
   defined globally. An example below:
   
   [source,java]
  
positive.code: -----------------------------------------------------------
  
  You can identify if the Exchange is an
  *onCompletion* Exchange as Camel will add the
  property `Exchange.ON_COMPLETION` with a boolean value of `true` when it
  spin-off the *onCompletion* Exchange.
  
  [[OnCompletion-UsingonCompletionfromSpringDSL]]
  === Using onCompletion from XML DSL
  
  The onCompletion is defined like this with XML DSL:
  
negative.code: </route>
  ----
  
  IMPORTANT: If an OnCompletion is defined in a route, it overrides *all* global
  scoped and thus it is only the route scoped that are used. The globally
  scoped are not in use.
  
  === Using onCompletion with onWhen predicate
  
  As other DSL in Camel you can attach a predicate to
  the OnCompletion so it only triggers in certain conditions, when the
  predicate matches. For example to only trigger if the message body contains the word
  _Hello_ we can do like:
  
  [source,java]
  ----
  