This chapter deals with structure loops, not Process loops.
To enable the repetition of certain parts of a Scenario, we use transitions to go “back in time”. Transitions are instantaneous intervals that can connect two states regardless of their chronological relationship.
In this case, the loop will go on forever as well as playing and replaying all following intervals.
For more control and to avoid perpetual looping and branching, it may be necessary to isolate a repeating structure in a sub-scenario. Triggering the end of the interval containing the sub-scenario will ensure that the loop stops as well as the execution of the following intervals.
Adding a trigger on the last
Sync of a loop and setting its maximum duration allows to control the amount of repetition. The trigger left by default to be “never” true will still be validated when the maximum duration of the preceding interval has been reached. With this method, the time spent looping is equal to the loop duration + the maximum duration, and can be fine-tuned by manipulating the closing parenthesis.
Transitions actually connect to
Syncs (vertical doted lines), thus, transitioning to a specific
Sync will execute or re-execute all connected branches. When several transitions are connected to the same
Sync, the smallest loop will then always restart first and cut short all parallel intervals.
Transitions can provide a workaround in this situation. Since transitions are instantaneous intervals, they can also be used to isolate parallel loops without interfering with timing and their original synchronization.