Are you re-deploying the workflow after every change? Unless you have auto-deploy turned on, which you can tell because you'll have a bunch of versions of your workflow definition in the workflow console, you must re-deploy.

Steps:

1. Deploy your AMP

2. Open the workflow console and do "deploy activiti alfresco/module/workflow-tutorial-platform-jar/workflow/helloWorld.bpmn". Note: I'm guessing on the path--it's a classpath and I don't recall off the top of my head if what I'm showing here is correct but this gets you pointed in the right direction.

3. Test your workflow

4. Need to make a change? Make your change, build, go back to step 1.

The tutorial sets "redeploy" to false in the Spring Bean. You can change that to true if you want, then you can skip step 2. But when your code stabilizes, change back to false, otherwise you'll get a TON of unnecessary versions of your workflow definitions over time.

Are you re-deploying the workflow after every change? Unless you have auto-deploy turned on, which you can tell because you'll have a bunch of versions of your workflow definition in the workflow console, you must re-deploy.

Steps:

1. Deploy your AMP

2. Open the workflow console and do "deploy activiti alfresco/module/workflow-tutorial-platform-jar/workflow/helloWorld.bpmn". Note: I'm guessing on the path--it's a classpath and I don't recall off the top of my head if what I'm showing here is correct but this gets you pointed in the right direction.

3. Test your workflow

4. Need to make a change? Make your change, build, go back to step 1.

The tutorial sets "redeploy" to false in the Spring Bean. You can change that to true if you want, then you can skip step 2. But when your code stabilizes, change back to false, otherwise you'll get a TON of unnecessary versions of your workflow definitions over time.