-
Type:
Feature Request
-
Resolution: Won't Do
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
User Story (Required on creation):
Camunda offers multiple history levels (None, Activity, Audit, Full) and also provides functionality to write your own custom history level. There is a problem while trying to update this history level. Along with the change in config, a database change also need to be made in act_ge_properties table otherwise "historyLevel MisMatch exception occurs".
This makes deployments dependent on database change and increases complexity. Only config change should be sufficient to change the history level.
First we need to have the config and database in sync manually and then only we can deploy our code.
(This is the config)
camunda.bpm.history-level= full
Table name: act-ge_properties