Skip to content

Commit bd94597

Browse files
authored
Merge branch 'main' into rework-sizing-guide
2 parents 8c1a031 + 931a5fe commit bd94597

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versioned_docs/version-8.8/components/concepts/process-instance-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ You can migrate a called process instance in the same way as a regular process i
150150
## Migrate job worker user tasks to Camunda user tasks
151151

152152
:::important
153-
Only available since version 8.8.19
153+
Only available since version 8.8.20
154154
:::
155155

156156
You can migrate user tasks with a job worker implementation to Camunda user tasks by providing mapping instructions between the source and target user tasks.
@@ -438,7 +438,7 @@ In the following cases, the process instance can't apply the migration plan and
438438
- Multi-instance body limitations:
439439
- Each child instance of a multi-instance body should be migrated separately because they belong to another process instance.
440440
- It is not possible to migrate a parallel multi-instance body to a sequential multi-instance body and vice versa.
441-
- Mapping instructions can only change the user task implementation from a job-worker user task to a Camunda user task, but not vice versa (since 8.8.19, before that no user task implementation migration is possible).
441+
- Mapping instructions can only change the user task implementation from a job-worker user task to a Camunda user task, but not vice versa (since 8.8.20, before that no user task implementation migration is possible).
442442

443443
The following limitations exist that may be supported in future versions:
444444

0 commit comments

Comments
 (0)