topic Re: Changes to a custom workflow are not applied in Alfresco Archive

Changes to a custom workflow are not applied

lw7415 — Thu, 19 Feb 2015 23:28:16 GMT

I have a custom workflow that is deployed in Alfresco Community Edition 5.0.c as part of a larger package of mods. The workflow is deployed in a repository AMP and a Share AMP. In addition to the AMPs there are three email templates that are placed in a folder under /Data Dictionary/Email Templates.

Re: Changes to a custom workflow are not applied

douglascrp — Fri, 20 Feb 2015 00:56:42 GMT

In that case, you have 2 options.

Using the workflow console, you can run the commands bellow:

undeploy definition name activiti$customWorkflow
deploy activiti alfresco/extension/workflow/customWorkflow.bpmn

But as you are working on 5.0.c, you wont be able to run those commands, because workflow console was removed together with Alfresco Explorer.

The second option you have is to define your workflow register context file to redeploy your workflow on restart.
You can find a sample for this option here https://github.com/jpotts/alfresco-developer-series/blob/master/workflow/workflow-tutorial-repo/src/main/amp/config/alfresco/module/workflow-tutorial-repo/context/service-context.xml

Search for the tag <prop key="redeploy">false</prop>

If you set its value to true, it will redeploy your workflow definition on each restart.

Let me know if you need help to solve this issue.

Re: Changes to a custom workflow are not applied

lw7415 — Mon, 23 Feb 2015 16:37:19 GMT


<prop key="redeploy">true</prop> 
‍‍‍

fixed the issue. Thank you for the help!

Lw

Re: Changes to a custom workflow are not applied

douglascrp — Mon, 02 Mar 2015 03:01:45 GMT

Don't let that option set on production server, or you will have a new workflow definition version every single time you restart Alfresco.
Once you finished your development, set redeploy to false.