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: |camunda history level
  |camunda default value
  
  |`{properties-prefix}.history-level-default`
  |camunda history level to use when `history-level` is `auto` but the level can not determined automatically
  |default value from `history-level`
  
  |`{properties-prefix}.auto-deployment-enabled`
  |if processes should be auto deployed
  |`true`
  