anchor.diff:  }
   ----
   
  +IMPORTANT: When using `history-level auto` with more then one database and camunda version < 7.4 you have to provide a `JdbcTemplate` bean as `camundaBpmJdbcTemplate` corresponding to the `camundaBpmDataSource`.
  +
   ==== `DefaultHistoryConfiguration`
   
   Applies the history configuration to the process engine. If not configured the `camunda` default level will be used.
  
positive.code: * `org.camunda.bpm.spring.boot.starter.configuration.CamundaProcessEngineConfiguration`
  * `org.camunda.bpm.spring.boot.starter.configuration.CamundaDatasourceConfiguration`
  * `org.camunda.bpm.spring.boot.starter.configuration.CamundaHistoryConfiguration`
  * `org.camunda.bpm.spring.boot.starter.configuration.CamundaJobConfiguration`
  * `org.camunda.bpm.spring.boot.starter.configuration.CamundaDeploymentConfiguration`
  * `org.camunda.bpm.spring.boot.starter.configuration.CamundaJpaConfiguration`
  
negative.code:   return new CustomHistoryEventHanlder();
  }
  ----
  
  ==== `DefaultHistoryLevelAutoHandlingConfiguration`
  As camunda version >= 7.4 supports `history-level auto` this configuration adds support for versions < = 7.3.
  
  To have more control about the handling you can provide your own
  
  - `org.camunda.bpm.spring.boot.starter.jdbc.HistoryLevelDeterminator` with name `historyLevelDeterminator`
  
  IMPORTANT: The default configuration is applied after all other default configurations using the ordering mechanism.
  
  ==== `DefaultJobConfiguration`
  
  