Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
For some BPMN constructs, the runtime execution tree has changed from 7.2 to 7.3:
- Event Subprocess: used to be non-scope is now scope
- Seq Multi Instance Subprocess: this inner activitiy used to be non-scope, is now scope
- Multi Instance Receive Task: used to be non scope, is now scope
- Concurrency & non-interrupting events, used to be implemented based on executions which were both scope and concurrent, now an interleaved concurrent execution is used.
- we also need to tolerate broken execution trees as reported in
CAM-3727
We should start instances of these constucts in 7.2 and
- complete them in 7.3
- do error propagation in 7.3
- getActivityInstance tree should succeed and return "something remotely meaningful"
- I can delete the instance
Implementation note:
- also test something where an inner scope is created after migration, and then test the four aspects above
- test error propagation with catching boundary events as well as event subprocesses