If there are more than one process definitions for an App and I remove one of them (and Publish the App), everything is fine and process definition is also deleted in the Flowable database (it is not accessible via Flowable API).
However, if there is only one process definition for an App and I remove that from the App, it seems that it is removed from the App according to the Flowable Designer, but it is still present in the database and can be accessed via Flowable API.
Do I perform something wrong or is there a bug?
Are you using the Flowable Modeler (browser based application) for the process modeling?
If you publish an empty app from the Flowable Modeler then it won’t do anything.
What is the use case of doing this?
You can also delete deployments using the Flowable Admin app.
let me explain the situation we had.
we are using API and Modeller at the same time. We deploy some BPMNs using API and we check all these over Modeller or API but when we delete an app that has only one BPMN model, it is deleted from Modeller but not from API. In addition to that (another situation), let’s assume that we have an app which has only one BPMN model and if I delete the model (not app), everything seems OK on Modeller but not on API.
Is that a bug or something else?
Could you please provide me a way to overcome the problem I faced?
What do you mean ‘by API’? Once a process definition is deployed, it is stored as a Deployment/ProcessDefinition. The modeler uses Models. Thus, when deleting models, they will not delete the deployed artifacts. If you want to delete both, you’d need to programmatically delete both models and deployments at the same time.