Notification Wait Property Reference

• Parent process: The Notification Wait activity waits for some kind of notification from a Process Notification activity in a parent process ("Keep relation with child" property is enabled in the Process Creation to which the Notification Wait corresponds.)

• Child process: The Notification Wait activity waits for some kind of notification from a Process Notification activity in a child process. The Creation activity determines the Process Creation activity within the process. To achieve this scenario, the Notification Wait activity has to be located between the Process Creation activity and the Termination Wait activity -this last one, if applicable- as Notification is expected from an instance generated in a child process (the process which the Process Creation calls) ("Keep relation with child" property is enabled.)

• External event: The Notification Wait activity waits for notification from an external program using PAPI (for further information, see the PAPI Javadoc distributed with the product) or an activity in an external process using the send method from the Notification component (For further information, see the Notification Component documentation.)

Allows interruptions: the Notification Wait activity will behave as an exception catching activity with a remote control connected to the instance. An activity's BP-Method in the subprocess will send a notification with unique information to identify the correct instance to notify. This notification will be taken as an interruption and the instance will move from wherever it currently is and will go directly to the Notification Wait activity unless it has already reached the End activity. For further information, see Allowing interruptions on this page.

If this check box is selected, the Notification Wait activity appears with an interruption sign such as a small circle in its center in the Classic theme or a thunderbolt in the image (BPMN theme - ). This Activity can't be in the main flow.

Process notification immediately: speeds up the notification process. When this option is selected, the receiving activity's argument mapping will be run upon receipt of the notification. If it is disabled, the notification will be stored in a queue and its argument mapping will be processed in the order that it was added to the queue. This option is selected by default.

Once the Notification has been processed, any other notification for the same instance is dismissed when the instance arrives at the end. It means that if two notifications for the same instance are sent, the first one to arrive will notify the instance and the second one will have no effect, unless the instance passes through this activity again.