Camunda BPMN Versioning Issue

[rohit74]

I’m facing a situation where adding a new bpmn file to resources folder is making version of existing workflows to increase by 1. Is this the expected behaviour of camunda?

Eg:

I had three workflows initially, Workflow_1.bpmn, Workflow_2.bpmn, Workflow_3.bpmn. Once I tried to add another workflow file Workflow_4.bpmn, version of each of workflows 1, 2 and 3 increased by 1 i.e. after deployment version of existing workflows became 2 and Workflow_4.bpmn was deployed with version 1. What should be done to prevent updation of existing workflows.

2. Is there any way I can identify that if there is no change in existing workflow then on which ground camunda identified them as a new version of workflow and done required changes in the version.

I’m already aware that we can download different versions of workflow file from deployment page of cockpit itself and also by using below api to compare if there is any change in workflow files.

http://localhost:8080/engine-rest/process-definition/{processDefinitionId}/xml

So, I’ve already downloaded and compared the existing workflow files with new version and I found there was no change, then why camunda updated the version number of existing workflows?

Thanks for any help you can provide!!

[Ingo_Richtsmeier]

Hi @rohit74,

@rohit74

I’m facing a situation where adding a new bpmn file to resources folder is making version of existing workflows to increase by 1. Is this the expected behaviour of camunda?

it is expected as the default setting for isDeployChangedOnly is false: Process Archive Configuration | docs.camunda.org

It depends on the packaging of the process engine (shared engine, embedded in Spring boot, standalone in Camunda Run) and the usage of process applications where to apply the setting. Which packaging did you choose?
Do you use a process application?

@rohit74

Is there any way I can identify that if there is no change in existing workflow then on which ground camunda identified them as a new version of workflow and done required changes in the version.

The engine does it for you if you change the default setting.

Hope this helps, Ingo

[rohit74]

Hi @Ingo_Richtsmeier,

Thanks for responding. I’ve one more query on your response point

—>It depends on the packaging of the process engine (shared engine, embedded in Spring boot, standalone in Camunda Run) and the usage of process applications where to apply the setting. Which packaging did you choose?
Do you use a process application?
Yes I’m using process application for deployment. It’s an spring boot project where I’m placing all
the bpmn files inside /src/main/resources folder of the project.

As you said if I enable this property isDeployChangedOnly, then what will be it’s implications

1. Will my further changes in existing workflows(say addition of an external task, user task or timer) will not create a new version?
2. Will it affect any of the running instances on previous versions?

[Ingo_Richtsmeier]

Hi @rohit74,

@rohit74

Yes I’m using process application for deployment. It’s an spring boot project where I’m placing all
the bpmn files inside /src/main/resources folder of the project.

In this case you have fill the processes.xml with the requested XML structure and the property with the desired value.

@rohit74

Will my further changes in existing workflows(say addition of an external task, user task or timer) will not create a new version?

Each change of a single character in the XML will create a new version on deployment. Even moving an activity a single pixel will change the coordinates in the XML structure.

@rohit74

Will it affect any of the running instances on previous versions?

No. The setting applies only to new deployments.

Hope this helps, Ingo

[rohit74]

Hi @Ingo_Richtsmeier,

It worked, I made desired changes in process.xml, tested it and everything is working fine.

Thanks for your quick response