Updating single BPMN creates new Process Definition versions for all

Flowable Engine
1

I have multiple BPMN xml processes defined in my application.
Whenever I make a change to one process, it creates new versions for all of them.
Ex.
FirstProcessDef:1:c9668b6d-f5f7-11eb-868e-a2f90529e897
FirstProcessDef:2:3a7ba179-f5f7-11eb-97aa-a2f90529e897
SecondProcessDef:1:3a7b7a68-f5f7-11eb-97aa-a2f90529e897

Making a change in SecondProcessDef.bpmn, or adding a new bpmn process, will create a new version for both.

Result:
FirstProcessDef:1:c9668b6d-f5f7-11eb-868e-a2f90529e897
FirstProcessDef:2:3a7ba179-f5f7-11eb-97aa-a2f90529e897
FirstProcessDef:3:399bc8c3-f5f7-11eb-97aa-a2f90529e897
SecondProcessDef:1:3a7b7a68-f5f7-11eb-97aa-a2f90529e897
SecondProcessDef:2:399bc8c3-f5f7-11eb-97aa-a2f90529e897

I would like some help in only creating new Process Definition versions for only the bpmn that was changed. If a new bpmn process is added, the existing processes should not have new version created for them.

2

Hey @wbgreely,

I guess you are referring to the auto deployment functionality when an application boots up. By default Flowable will use a single deployment for all resources.

However, there is an option to change that and use a single-resource mode. In order to do that you will need to do something like:

@Bean
public EngineConfigurationConfigurer<SpringProcessEngineConfiguration> customEngineConfigurer() {
    return engineConfiguration -> {
        engineConfiguration.setDeploymentMode("single-resource");
    }
}

Cheers,
Filip

1 Like
3

@filiphr This did the trick. Thanks!