-
Type:
Feature Request
-
Resolution: Won't Fix
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: engine
-
None
At the moment, there are transition instances for asyncBefore and asyncAfter jobs. If there can be both for an activity, it is currently not possible to distinguish a transition instance that is leaving the activity from a transition instance that is entering the activity via public API.
Solution idea:
- Extend the TransitionInstance interface accordingly