topic How to avoid concurrent auto deployment by multiple developers in Activiti local in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177511#M130641 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><SPAN>When multiple developers perform concurrent auto deployment of the BPM process in Activiti, changes made by one user will be overridden by other user in local. </SPAN><BR /><BR /><SPAN>Can we use tenant_id to start process to show the processes to the user for the deployments made by his ID alone?</SPAN><BR /><SPAN>Is there any better approach to address this issue?</SPAN></BODY></HTML> Sat, 02 May 2015 09:50:00 GMT chockyc91 2015-05-02T09:50:00Z How to avoid concurrent auto deployment by multiple developers in Activiti local https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177511#M130641 Hi,When multiple developers perform concurrent auto deployment of the BPM process in Activiti, changes made by one user will be overridden by other user in local. Can we use tenant_id to start process to show the processes to the user for the deployments made by his ID alone?Is there any better appr Sat, 02 May 2015 09:50:00 GMT https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177511#M130641 chockyc91 2015-05-02T09:50:00Z Re: How to avoid concurrent auto deployment by multiple developers in Activiti local https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177512#M130642 <HTML><HEAD></HEAD><BODY><SPAN>Yes, you can use tenantId to deploy process definitions, start process instances, and to retrieve process instances. But note that using tenantId has implications that are mentioned in </SPAN><EM>18.4. Multitenancy</EM><SPAN> section of the user guide </SPAN><BR /><BR /><A href="http://activiti.org/userguide/index.html" rel="nofollow noopener noreferrer">http://activiti.org/userguide/index.html</A><BR /><SPAN> </SPAN><BR /><SPAN>Another approach is to make each developer use a specific prefix for the process definition key. For example&nbsp; developer1.myprocess, developer2.myprocess, and so on. Whether this is a better approach than using tenantId depends on you requirements.</SPAN></BODY></HTML> Sun, 03 May 2015 20:54:37 GMT https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177512#M130642 balsarori 2015-05-03T20:54:37Z Re: How to avoid concurrent auto deployment by multiple developers in Activiti local https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177513#M130643 <HTML><HEAD></HEAD><BODY><SPAN>&gt; Is there any better approach to address this issue?</SPAN><BR /><BR /><SPAN>Or, not use a shared database for development.</SPAN></BODY></HTML> Thu, 07 May 2015 12:45:26 GMT https://connect.hyland.com/t5/alfresco-archive/how-to-avoid-concurrent-auto-deployment-by-multiple-developers/m-p/177513#M130643 jbarrez 2015-05-07T12:45:26Z