Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(operate): refer to concepts page for limitations and supported elements for instance migration #4572

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −4
Open

docs(operate): refer to concepts page for limitations and supported elements for instance migration #4572

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/components/operate/userguide/process-instance-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Process instances can be migrated from one specific process definition version t
![operate-migrate-button](./img/process-instance-migration/migrate-button.png)

:::note
It is only possible to migrate running process instances, meaning instances in active or incident state. All other process instances will not be part of the migration plan and will be ignored.
It is only possible to migrate running process instances, meaning instances in active or incident state. All other process instances will not be part of the migration plan and will be ignored. Please visit the concepts section to learn about [all limitations](/components/concepts/process-instance-migration.md#limitations).
:::

The migration view features three areas: the source process diagram (top left), the target process diagram (top right) and the flow node mapping (bottom panel).
Expand All @@ -37,7 +37,7 @@ In this example, all service tasks from version 1 of `orderProcess` are each map
![operate-view-process-filters](./img/process-instance-migration/map-elements.png)

:::note
It is currently only possible to map service tasks, user tasks, subprocesses, call activities, and child instances. Mapping subprocesses to a different scope or mapping event subprocesses is not yet supported by Zeebe. To learn about all limitations, visit the [concepts section](/components/concepts/process-instance-migration.md#limitations).
It is currently only possible to map elements whose migration is supported by Zeebe. Visit the concepts section to learn about all [supported elements](/components/concepts/process-instance-migration.md#supported-bpmn-elements).
:::

6. (Optional) Click on a flow node in the diagram or on a source flow node row in the bottom panel to see how flow nodes are mapped.
Expand Down
4 changes: 2 additions & 2 deletions ...ned_docs/version-8.6/components/operate/userguide/process-instance-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Process instances can be migrated from one specific process definition version t
![operate-migrate-button](./img/process-instance-migration/migrate-button.png)

:::note
It is only possible to migrate running process instances, meaning instances in active or incident state. All other process instances will not be part of the migration plan and will be ignored.
It is only possible to migrate running process instances, meaning instances in active or incident state. All other process instances will not be part of the migration plan and will be ignored. Please visit the concepts section to learn about [all limitations](/components/concepts/process-instance-migration.md#limitations).
:::

The migration view features three areas: the source process diagram (top left), the target process diagram (top right) and the flow node mapping (bottom panel).
Expand All @@ -37,7 +37,7 @@ In this example, all service tasks from version 1 of `orderProcess` are each map
![operate-view-process-filters](./img/process-instance-migration/map-elements.png)

:::note
It is currently only possible to map service tasks, user tasks, subprocesses, call activities, and child instances. Mapping subprocesses to a different scope or mapping event subprocesses is not yet supported by Zeebe. To learn about all limitations, visit the [concepts section](/components/concepts/process-instance-migration.md#limitations).
It is currently only possible to map elements whose migration is supported by Zeebe. Visit the concepts section to learn about all [supported elements](/components/concepts/process-instance-migration.md#supported-bpmn-elements).
:::

6. (Optional) Click on a flow node in the diagram or on a source flow node row in the bottom panel to see how flow nodes are mapped.
Expand Down
Loading