In this process we have two concurrent executions, one executing the embedded subprocess and one executing the
In this process we have two concurrent executions, one executing the embedded subprocess and one executing the
"charge credit card" activity. Lets assume both executions are started and the first concurrent execution is waiting
"charge credit card" activity. Lets assume both executions are started and the first concurrent execution is waiting
for a user to complete the "review bookings" task. The second execution performs the "charge credit card" activity
for a user to complete the "review bookings" task. The second execution performs the "charge credit card" activity
...
@@ -5515,7 +5515,7 @@ public class MyTaskCreateListener implements TaskListener {
...
@@ -5515,7 +5515,7 @@ public class MyTaskCreateListener implements TaskListener {
<para>
<para>
The following is an example of an Event Sub-Process triggered using an error start event. The Event Sub-Process is located "at process level", i.e. is scoped to the process
The following is an example of an Event Sub-Process triggered using an error start event. The Event Sub-Process is located "at process level", i.e. is scoped to the process
@@ -5532,9 +5532,9 @@ public class MyTaskCreateListener implements TaskListener {
...
@@ -5532,9 +5532,9 @@ public class MyTaskCreateListener implements TaskListener {
As already stated, an Event Sub-Process can also be added to an embedded subprocess. If it is added to an embedded subprocess, it becomes an alternative to a
As already stated, an Event Sub-Process can also be added to an embedded subprocess. If it is added to an embedded subprocess, it becomes an alternative to a
boundary event. Consider the two following process diagrams. In both cases the embedded subprocess throws an error event. Both times the error is caught and
boundary event. Consider the two following process diagrams. In both cases the embedded subprocess throws an error event. Both times the error is caught and