Upgrade from 6.5 to 7.0

I am currently on version 6.5 and in the processing of migrating to version 7.0

I ran in sequence each of the database oracle upgrade scripts

6.5 to 6.6
6.6. to 6.7
6.7 to 6.7.1
6.7.1 to 6.7.2
6.7.2 to 6.8
6.8 to 7.0

Updated my pom

<properties>
    <maven-jar-plugin.version>3.2.0</maven-jar-plugin.version>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <java.version>17</java.version>
    <spring-security.version>6.2.1</spring-security.version>
</properties

<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>3.1.10</version>
</parent>

        <groupId>org.flowable</groupId>
        <artifactId>flowable-spring-boot-starter-rest</artifactId>
        <version>7.0.0</version>

Updated required code from java 11 to java 17

First question is this the correct approach to upgrade across multiple flowable releases ?

When I perform my spring-boot:run via intellij

I initially had the following in my config that I assume should have been set to false

engineConfiguration.setDatabaseSchemaUpdate(AbstractEngineConfiguration.DB_SCHEMA_UPDATE_TRUE);

which I assume is causing my checksum liquibase errors below ??

Second question
What is the best way to fix ?

Caused by: org.flowable.common.engine.api.FlowableException: Error initialising dmn data model
at org.flowable.common.engine.impl.db.LiquibaseBasedSchemaManager.initSchema(LiquibaseBasedSchemaManager.java:88) ~[flowable-engine-common-7.0.0.jar:7.0.0]
at org.flowable.dmn.engine.impl.db.DmnDbSchemaManager.initSchema(DmnDbSchemaManager.java:37) ~[flowable-dmn-engine-7.0.0.jar:7.0.0]
at org.flowable.dmn.engine.impl.cmd.SchemaOperationsDmnEngineBuild.execute(SchemaOperationsDmnEngineBuild.java:27) ~[flowable-dmn-engine-7.0.0.jar:7.0.0]
at org.flowable.dmn.engine.impl.cmd.SchemaOperationsDmnEngineBuild.execute(SchemaOperationsDmnEngineBuild.java:23) ~[flowable-dmn-engine-7.0.0.jar:7.0.0]

Caused by: org.flowable.common.engine.api.FlowableException: Error updating dmn engine tables
at org.flowable.common.engine.impl.db.LiquibaseBasedSchemaManager.schemaUpdate(LiquibaseBasedSchemaManager.java:129) ~[flowable-engine-common-7.0.0.jar:7.0.0]
at org.flowable.dmn.engine.impl.db.DmnDbSchemaManager.schemaUpdate(DmnDbSchemaManager.java:64) ~[flowable-dmn-engine-7.0.0.jar:7.0.0]
at liquibase.Scope.lambda$child$0(Scope.java:187) ~[liquibase-core-4.20.0.jar:?]
at liquibase.Scope.child(Scope.java:196) ~[liquibase-core-4.20.0.jar:?]
at liquibase.Scope.child(Scope.java:186) ~[liquibase-core-4.20.0.jar:?]
at liquibase.Scope.child(Scope.java:165) ~[liquibase-core-4.20.0.jar:?]

Caused by: liquibase.exception.ValidationFailedException: Validation Failed:
2 changesets check sum
org/flowable/dmn/db/liquibase/flowable-dmn-db-changelog.xml::7::flowable was: 7:4b6469565b1b00b428ffca7eab1ef253 but is now: 8:215a499ff7ae77685b55355245b8b708
org/flowable/dmn/db/liquibase/flowable-dmn-db-changelog.xml::8::flowable was: 7:f83b7b3228be2c4bbb554d6de45307d7 but is now: 8:5355bee389318afed91a11702f2df032
at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:357) ~[liquibase-core-4.20.0.jar:?]

Hey @pt35468,

This looks like some issues with the Liquibase version. Have you managed to resolve your issue?

Cheers,
Filip