HistoryLevel in Activiti 5.4

[frauke]

Hello everyone,

I got the problem "no historyLevel property specified" on starting the web server (Tomcat).
So I changed the spring  setting of processEngineConfiguration so it defines the historyLevel.
But now it expects an Integer instead of a String.

My question now is:
How does the "historyLevel" settings are related (if they indeed are!?) to the former "history" settings which had the values "audit", "full" etc.
What value do I have to set if formerly I used history="full"?

Frauke

[frederikherema1]

Right… Forgot about that (it's my comment on the other topic, woops). That's why the java-steps in the upgrade-process are introduced. But other than that, the properties are completely unrelated.

The history-level is now stored in the DB, the first time the engine starts on a schema (or upgrades) to prevent changing the history-level and messing up engine assumptions done about history (eg. expecting certain entities to exist when level=full). I thought you were migrating from 5.3 to 5.4, which contains no java-steps, only SQL.

I guess, since you use liquibase, you will have to check all java-steps in the upgrade-process and do that stuff manually…

[frauke]

Well yes, it was your comment - I forgot to mention in my post 
but still it was a very good one and helpful too.

We are thinking about calling the DbUpgradeStep classes from Liquibase using some kind of wrapper class, there is a possibility to do that.
I will try that and if it works, I will post it here. May be it will be interesting for other users too.

And by the way: I didn't really believe those properties where related directly in any way 

Frauke