-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
What/Where is the issue ?
In C7, process instances can be migrated to a newer process version in the engine during their execution. The version displayed on the process instance in Optimize, however, does not get updated until the process instance is completed.
Environment: C7
Optimize version : All
ES version : All
OS + Browser version : All
Steps to reproduce:
- Preconditions:
- Steps:
- Deploy version 1 of a process and start an instance with multiple tasks (don't complete it - it needs to be running)
- Observe the data in Optimize in a report filtering for version 1
- Deploy version 2 of a process and migrate the running instance to v2
- Observe the data in Optimize in a report filtering for version 1. Observe that it is not present in a report filtering for version 2
- Complete the instance
- Observe the data in Optimize in a report filtering for version 2. Observe that it is not present in a report filtering for version 1
Observed behavior:
Running instances that are migrated in the engine are not migrated in Optimize until they are completed
Expected behavior:
Running instances that are migrated in the engine are also migrated in Optimize
Additional Information:
We can get the process definition ID for each of the import DTOs that make up a process instance. Using this, we might be able to determine if an instance has been migrated. It is unlikely that Optimize can know about the migration of a process instance until more data is imported for the instance, so some delays in Optimize might be inevitable.