cancel
Showing results for 
Search instead for 
Did you mean: 

CallActiviti with tenant Id

nik10_mah
Champ in-the-making
Champ in-the-making
Hi,

I have deployed a two processes one is MP and  other is AP where MP calls AP using Call Activiti element. And both processes have been deployed with tenantId. Now when i try to start activiti MP process and when the call Activiti element encountered in this process it given ActivitiObjectNotFoundException from AP process. Although i have deployed both the definitions simultaneously.

One i thing i have also noted that for a definition deployed using tenant id one has to pass the tenantId to start the definition otehrwise it will throw the activitiObjectnotfound exception. So it seems like whne using callActiviti attribute in bpmn file it is calling another activiti without tenant id that why it is giving ActivitiObjectNotFound exception. So possibly we might have to pass the tenantId somewher with callActiviti element of bpmn. PLease let me know if i m worng and guide me in right direction. I also tried with passing a tenentId as processVariable while starting MP(which call AP) but it still doesn't worked during CallActiviti.

Thanks
6 REPLIES 6

trademak
Star Contributor
Star Contributor
Hi Nikhil,

It could be that you ran into a bug with the tenant support.
Could you create a JIRA issue? We'll look into it.

Best regards,

nik10_mah
Champ in-the-making
Champ in-the-making
Hi, I have attached the bpmn files and the test case.
Please let me know if you need anything else.

nik10_mah
Champ in-the-making
Champ in-the-making
Could you please tell me of resolving this bug in near future. I am currently using multitenancy in my project and i really need this. Or is there any workaround for this.

jbarrez
Star Contributor
Star Contributor
You are correct: you indeed found a bug.

Thanks by the way for the excellent unit test. If all bug reports were like this …

I fixed the bug on master: https://github.com/Activiti/Activiti/commit/03ea540a321b9aec7c3782761c084d6e530354fb

There is a workaround: you can use the activityBehaviourFactory to replace the default CallActivityBehaviour with the code of the CallActivitiBehaviour in the commit above.

penusila611621
Champ in-the-making
Champ in-the-making
We are using Activiti 5.15.1 version & I am not seeing the change you have done in CallActivityBehavior.java and DeploymentManager.java as part of work around. Which version having these changes if not, how to make these changes.

jbarrez
Star Contributor
Star Contributor
Github (click on the url i pasted above) clearly shows it was part of 5.16.