We have 3 bpmn file (difference project & unique process definition). We use the same DB Schema, & use spring boot camunda too.
The weird thing is when we hit the service through first project, why it seem like trigger the difference Bpmn.
Say
Project A has A1 BPMN process definition
Project B has B2 BPMN process definition
When we hit project A through spring boot custom rest, it seem searching B2 BPMN, and throw error
Caused by: org.camunda.bpm.engine.impl.javax.el.PropertyNotFoundException: Cannot resolve identifier âvalidateItemDelegateâ.
This fail delegate is service task (sequential multi instance).
The two project run at the same time, and one DB Schema, and this exception was found in project B.
When we hit the custom rest we trigger this
ProcessInstantiationBuilder processBuilder = camunda.getRuntimeService().createProcessInstanceByKey(âuniqueKeyA1â);
it should call the first A1 BPMN not B2 BPMN. (I have difference the process definition key)
Is there some configuration that need to be done when using sequential multi instance?
Or is there general configuration that need to be added in each project.
This wouldnât happend if only one project is running, but we need to run the two project at the same time.
Use camunda 7.13.0 and spring boot 2.1.5
Thank You.