In the example above, the
boundary event behaves exactly like a scope
handler. The same processing rule applies: activities in the main scope execute in parallel with the
activity, if the alarm is triggered. This makes the boundary event non-interrupting. The linked activity (the reply in the above example) cannot be not part of the main process.