Currently I get a headache thinking about a process upgrade (new version) of a webMethods-BPM-process.
I know that a process instance always runs in the process-version it was started with. I also know that after the deployment of a new version of a process all new process-instaces are based on the new version.
As long as the interfaces of the process do not change between versions everything is fine. But enough about paradise…
In my world the interfaces change - always. That leads to the point where I have two possibilities:
- Implement compability code with each update in each used/changed interface - this will lead to a very ugly codebase after multiple updates…
- Update the process-instances.
I would like to try the second approach - but I have no idea how. Parse the process state and create a new one?
Did someone solve my problem with webMethods?
Any help is appreciated!