Waiting Triggers

When a simulation reaches a point where any change of state (for any thread) requires a Trigger to proceed, the simulation is effectively paused and control returns to Enterprise Architect. The simulation is now effectively waiting for some form of event (real world signal) to proceed.  The Waiting Triggers list is now useful in helping to determine which Trigger should be manually signalled.

Access    Analyzer | Breakpoints & Events > Simulation Events

The Waiting Triggers list on the Simulation Events tab is

Populated on each Simulation cycle with any Triggers that would have an immediate effect if signalled
Populated with a discrete set (any duplicates are not shown as a Trigger is effectively broadcast to all transitions at once)
Activated by double clicking on the Trigger of interest
Includes all possible triggers - including those activating transitions on parents of currently nested states


The example below shows the current simulation has hit a point where two possible Triggers may influence the flow of execution. Due to the nature of Triggers and their effects, the list below may refer to the following example situations equally validly:

A single state has two outgoing transitions which are respectively waiting for Hold and Pushdown. Firing one of these will activate the associated transtion in the simulation
Two (or more) threads (concurrent regions) each have a state waiting on either Hold or Pushdown. Firing one of these triggers will result in the thread(s) waiting on that trigger to proceed while the other thread(s) will remain blocked.
A child state is waiting on one of the triggers while a parent state is waiting on the other. Firing a trigger will result in the associated transition being fired and either the child or parent proceeding respectively.
Any combination of the above




Learn more