Currently it seems that PIM service doesn't account for a Migration Plan with different source and target process ids.
There are a few things to consider:
- That already reveals a disconnect between UI and service, because in UI such plan can be created at least (further usage of such plan is subject of some of the linked issues).
- This way we're preventing following use cases:
- possibility to rename project/deployment and then migrate the instances
- rename a process and then migrate the instances
- possible combination of both (e.g. moving from legacy project to a new implementation)
I understand that in case of an implicit migration (either during product upgrade or when using the service alone) this is understandable limitation. But with addition of UI, where such information can be tracked and presented, I see this as a serious limitation of scope of use cases.
- causes
-
JBPM-8498 PIM UI - Migration Plan edit puts incorrect data into edit form
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- duplicates
-
-
- Resolved
-
