topic Deploying Workflows with Delegates - Can't Delete in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/deploying-workflows-with-delegates-can-t-delete/m-p/151424#M106181 <HTML><HEAD></HEAD><BODY><SPAN>Hi - we're using activiti-explorer to manage our workflows.&nbsp; We uploaded a new workflow that contains dependencies on Java delegates.&nbsp; We uploaded the new workflow using the "Processes" tab and deployed it.&nbsp; There were no problems with this.&nbsp; Once we wanted to delete the deployment, we noticed we forgot to put the Java delegates into the classpath of the engine.&nbsp; As such, we were informed we could not delete the deployed workflow.</SPAN><BR /><BR /><SPAN>As a work-around, we went to the database directly and deleted the necessary entries to clean it up.</SPAN><BR /><BR /><SPAN>Is there a way to delete these workflows that may not have the proper classpath entries?&nbsp; Better yet…&nbsp; is there a way to prevent the workflows from being deployed unless the necessary delegate classes are in the classpath?</SPAN><BR /><BR /><SPAN>Thanks.</SPAN></BODY></HTML> Fri, 02 Aug 2013 19:20:39 GMT zoikks1 2013-08-02T19:20:39Z Deploying Workflows with Delegates - Can't Delete https://connect.hyland.com/t5/alfresco-archive/deploying-workflows-with-delegates-can-t-delete/m-p/151424#M106181 Hi - we're using activiti-explorer to manage our workflows.&nbsp; We uploaded a new workflow that contains dependencies on Java delegates.&nbsp; We uploaded the new workflow using the "Processes" tab and deployed it.&nbsp; There were no problems with this.&nbsp; Once we wanted to delete the deployment, we noticed we fo Fri, 02 Aug 2013 19:20:39 GMT https://connect.hyland.com/t5/alfresco-archive/deploying-workflows-with-delegates-can-t-delete/m-p/151424#M106181 zoikks1 2013-08-02T19:20:39Z Re: Deploying Workflows with Delegates - Can't Delete https://connect.hyland.com/t5/alfresco-archive/deploying-workflows-with-delegates-can-t-delete/m-p/151425#M106182 <HTML><HEAD></HEAD><BODY><SPAN>In the beginning, we had additional checks at deploy-time to see if the needed classes were on the class path. But we reverted that, due to the fact one can do "deploys" from other engines than the actual engine running the workflows. This was too restrictive, so we got rid of it.</SPAN><BR /><BR /><SPAN>One solution would be to alter the actual ACT_GE_BYTEARRAY entry for that deployment (!! when engine is down), removing the offending listeners. After booting the engine, you can delete the process and everything is nicely cleaned up the way it should (cascading all related entities). Another approach would be to migrate the process-instances to a newer version, which don't have the wrong class-pointers in it (using SetProcessDefinitionsCmd, search forum for this), so they are running in a process that can be deleted.</SPAN></BODY></HTML> Mon, 05 Aug 2013 08:31:56 GMT https://connect.hyland.com/t5/alfresco-archive/deploying-workflows-with-delegates-can-t-delete/m-p/151425#M106182 frederikherema1 2013-08-05T08:31:56Z