[SOLVED] Publishing app causes org.flowable.common.engine.api.FlowableException: The deployment contains process definitions with the same key (process id attribute), this is not allowed

1

Hello.

I am using Flowable 6.5.0, and I have this main process containing a CallActivity step.
I have used the Flowable modeler to draw both the main and the secondary processes.
When I try to create an App, including both processes, when I try to deploy it, I got the error message:
2020-02-28 11:06:23.738 INFO 17781 --- [nio-9080-exec-9] o.f.a.e.i.d.AppDeployer : Processing app resource analise-credito-app.app 2020-02-28 11:06:23.740 INFO 17781 --- [nio-9080-exec-9] o.f.e.c.i.d.BpmnDeployer : BpmnDeployer: processing resource analise-credito.bpmn 2020-02-28 11:06:23.741 INFO 17781 --- [nio-9080-exec-9] o.f.e.c.i.d.BpmnDeployer : BpmnDeployer: processing resource formalizacao-proposta-credito.bpmn 2020-02-28 11:06:23.893 ERROR 17781 --- [nio-9080-exec-9] o.f.c.r.e.BaseExceptionHandlerAdvice : Unhandled exception org.flowable.common.engine.api.FlowableException: The deployment contains process definitions with the same key (process id attribute), this is not allowed

What is the right way to deploy an App into the same Flowable process I am using to draw the processes?

If I create the App containing only the main process, the deploy works, but when I execute it, when the CallActivity is reached, the following error happens:

org.flowable.common.engine.api.FlowableObjectNotFoundException: Process definition formalizacao-proposta-credito was not found in sameDeployment[false] tenantId[] fallbackToDefaultTenant[false]

Thank you.

2

It seems there is a problem both with the export app as zip and also as the import and publish actions, as both processes have different process ids, (formalizacao-proposta-credito and analise-credito), but when I export the zip, checking the bpmn files, I see both are set as “process”.
I even tried to edit the bmpn files, setting again the correct process id, as follow:

But even after that, changing the bmpn files and “zipping” the folder again, when I imported it, both were again set as “process”.

Then, inside flowable-modeler, I have set again the correct ids, edited the imported app to have the new versions, and tried to publish, and again, the same error, “same key (process id attribute), this is not allowed”.

Is this a new bug? Have anyone tried to use the new version 6.5 already?

3

The problem was in the json file exported with the bmpn file.
The process id inside of it was set as process.

What I don’t understand is why it got exported like that, if the process id was set in the processes.

4

I am doing POC on this, but seems flowable is not working as expected.
I am getting the same error, with flowable-ui docker running, when I deploy an application, the category is lost and process definition key is always set to process.
Does anybody has a solution to this?