-
Notifications
You must be signed in to change notification settings - Fork 197
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.
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
Support process instance migration with active user tasks #3311
Conversation
Zeebe 8.5.0-alpha1 support migration of user tasks. Regardless of implementation type (job worker or zeebe user task).
Process instance migrations that attempt to change the implementation of a task (for example from a job worker user task to a zeebe user task) are rejected by Zeebe.
The values of a zeebe user task don't change on migration.
As static values are defined by the Expressions concept page as something different from expressions, we should explicitly highlight that static values are also left unchanged after migrations.
👋 🤖 🤔 Hello! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.4/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@korthout LGTM! 🚀
I added one suggestion, feel free to apply or skip it. 👍
@@ -152,6 +154,7 @@ The following limitations exist that may be supported in future versions: | |||
- An element that becomes nested in a newly added sub-process | |||
- An element that was nested in a sub-process is no longer nested in that sub-process | |||
- Mapping instructions cannot change the element type | |||
- Mapping instructions cannot change the task implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔧 @korthout Would be good if we give and explanation of this. We can say something similar to "e.g. user task implementations (zeebe user task and job based user task)".
1e88a1d
@christinaausley Please have another look, and feel free to merge it |
Description
Zeebe and Operate
8.5.0-alpha1
support the migration of process instances with active user tasks.Both task implementations are supported:
Job worker
Zeebe user task
Mapping instructions cannot change the task implementation.
All values of a job or a 'zeebe user task' are left unchanged after migration.
closes camunda/camunda#15964
When should this change go live?
hold
label or convert to draft PR)?PR Checklist
/versioned_docs
directory, or they are not for an already released version./docs
directory (aka/next/
), or they are not for future versions.