So you have a couple of workflows already deployed to Production, and have hundreds of active processes running. One day your Business User comes to you and says: "Can we do X and Y and then also R,S,T, U while you're making the changes.."
Fine, you think. OK, a couple of days later you deployed the new workflow, and THEN your Business User says: "Look there's a system bug and the issue is not fixed. How come my process is still doing A and B? I thought you have already made changes???"
err.... didn't I already mention that the change would only apply on NEW processes? LOL.
Now here's what you need to do to remedy it!
1. Go to Enterprise Manager, locate any process running on prior version, Suspend it, Migrate it, and Save the instruction file. The resulting instruction file (.xml) can be found in the AgilePoint/EnterpriseManager/tmp/ folder. Continue the process.
2. Now Remote into the AgilePoint server and launch Command Prompt. Navigate to AgilePoint/AgilePointServer/Tools/
3. Run this command once: apadm.exe. For some reason, if you run (4) without this prior step, it's always going to result in an error.
4. Run the following command: apadm -mgproc "Path to XML
5. REPEAT THIS for every prior version and every different stage.
No printscreens. If you're an AgilePoint Administrator you already know what I am talking about, and you could refer to their online documentation for more. If you're not... then you probably won't need be reading this to begin with anyway.
