1 of 1 people found this helpful
In my opinion, this is correct behavior as as soon as error is thrown the error boundary event catches it and since this is an error event it will cancel activity it is attached to (the exchange rate subprocess) and by that making the event subprocess included in it not active. That makes it unavailable to receive signals. Thus it does work as expected. Event subprocess will be active as long as its container is active.
Thx for that clarification. From that perspective, that makes sense for me.
Would that situation change when switching to compensation boundary events? Because when doing that, neither the first nor the second model triggers the compensation event subprocess. With your explanation, that kind of makes sense for the second scenario. With the first scenario, I receive the following error message:
unable to parse xml : Exception class java.lang.IllegalArgumentException : Compensation Event Sub-Processes at the process level are not supported.
Can someone clarify that for me?
I guess it's caused by unfinished work on compensation support so it might still not fully provide capabilities you would expect. Hopefully 6.2 will get more support for compensation though it's still not there