You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Process instances that are not on the current version of the process model are always migrated to the current version. The version tag is used for this purpose.
Under certain circumstances there may be several deployments of the last version (tag) and then it can happen that the instances of all are on the last version, but not necessarily on the last deployment/process definition.
This is irritating when you look in the cockpit for the instances of the last version tag. Could the migrator be adapted so that it also takes this into account?
The text was updated successfully, but these errors were encountered:
Process instances that are not on the current version of the process model are always migrated to the current version. The version tag is used for this purpose.
Under certain circumstances there may be several deployments of the last version (tag) and then it can happen that the instances of all are on the last version, but not necessarily on the last deployment/process definition.
This is irritating when you look in the cockpit for the instances of the last version tag. Could the migrator be adapted so that it also takes this into account?
The text was updated successfully, but these errors were encountered: