priint-bpm Migration Note: Camunda History Level Mismatch

During migration/update, make sure that the history-level configured in application.yml matches the value already stored in the database.

If the act_ge_property table contains a record with name_ = 'historyLevel' and its value does not match the history-level configured in application.yml, priint-bpm will fail to start with an error similar to the following:

org.camunda.bpm.engine.ProcessEngineException: historyLevel mismatch: configuration says HistoryLevelAudit(name=audit, id=2) and database says HistoryLevelFull(name=full, id=3)

In this case, you must either adjust the history-level in application.yml so that it matches the database value, or update the database entry so that it matches the value configured in application.yml.

The values in application.yml correspond to the numeric values in the database as follows: NONE = 0, ACTIVITY = 1, AUDIT = 2, FULL = 3.

For example, if your target configuration is AUDIT, you can update the database with the following SQL statement:

update act_ge_property
set value_ = 2
where name_ = 'historyLevel';