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(all three deployed in one go). 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.
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?
Framework: Spring Boot