Process migration

I’m just looking at how to migrate one of our process definitions and I’m not sure on the best approach as using the migration rest api I get ‘Activities have incompatible types’.
I have attached below a very much striped down version of the original version and what we need to migrate any running processes to.

I’ve colour coded where version 1 needs to map on to version 2 which are causing the error (I think the call activities Send message 1/2 and process data should map fine as the underlying process hasn’t changed and are still of the same type).

Any pointers in how this should be achieved would be much appreciated.



Any solution did you got for this problem?
I am facing similar problem.

I did not try this, but I think that if you want to migrate something that has incompatible type with the second one, you should try to model the same type of the first (migrating) activity (some dummy just for migration purposes), in front of the desired element, just for the “landing” of the migrating tokens, so that they can pass through to the “desired activity” (you can remove this in the next version of your process)
But I am not sure how about the signal event in the version one.
Hope this helps.

1 Like