-
Type:
Task
-
Resolution: Fixed
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: engine
-
None
Issue 1: Process instances containing asynchronous continuations before or after tasks with mi-loop characteristics:
the achtityId property in the job definition used to reference the inner activity. Starting from 7.3 it should reference the Mi-Body.
We need to write testcases in which we deploy such a process with 7.2 and assert the expected behavior after parsing.
Expected behavior:
- the job definitions are "migrated" meaning that the activityId in the job definition is adjusted to the activity id of the mi-body
===
Issue 2: async jobs before multi instance tasks created in 7.2 reference the inner activity; when executing these jobs with 7.3, they won't execute the multi-instance body, thus simply executing the inner activity once. Reason: the execution entity referenced by the job points at the inner activity.
Expected behavior:
- when such a job is executed, the execution is set to the multi-instance body first
===
Note: asyncAfter on multi-instance activities is seriously broken in 7.2.0, so I won't create a migration test.
This is the controller panel for Smart Panels app
- is related to
-
CAM-3851 Cannot use asyncAfter on multi instance activities
-
- Closed
-