HistoryLevel.HISTORY_LEVEL_ACTIVITY is deprecated

Camunda 7 Topics Discussion & Questions
1

Since from which camunda version HistoryLevel.HISTORY_LEVEL_ACTIVITY is deprecated?

if (HISTORY_VARIABLE.equalsIgnoreCase(history)) {
      historyLevel = HistoryLevel.HISTORY_LEVEL_ACTIVITY;
      LOG.usingDeprecatedHistoryLevelVariable();
}

Also if I set multiple history level, then for which history level the process engine gives preference? Everything or one?

if (historyLevels == null) {
      historyLevels = new ArrayList<HistoryLevel>();
      historyLevels.add(HistoryLevel.HISTORY_LEVEL_NONE);
      historyLevels.add(HistoryLevel.HISTORY_LEVEL_ACTIVITY);
      historyLevels.add(HistoryLevel.HISTORY_LEVEL_AUDIT);
      historyLevels.add(HistoryLevel.HISTORY_LEVEL_FULL);
  }

  if (customHistoryLevels != null) {
      historyLevels.addAll(customHistoryLevels);
  }
1 Like
2

Hi @aravindhrs,

There is no deprecation here: camunda-bpm-platform/engine/src/main/java/org/camunda/bpm/engine/impl/history/HistoryLevel.java at 7.11.0 · camunda/camunda-bpm-platform · GitHub

The constant org.camunda.bpm.engine.ProcessEngineConfiguration.HISTORY_VARIABLE is deprecated, because it has the exact same effect as HISTORY_ACTIVITY. I haven’t checked, but I guess it is deprecated since 7.0.

The engine choose the history level that matches the name configured via the history property. If there are multiple such levels, then any of those is chosen.

Cheers,
Thorben

1 Like
3

@thorben thanks for your clarification. As you said, the constant org.camunda.bpm.engine.ProcessEngineConfiguration.HISTORY_VARIABLE is deprecated.

4