Designing and Managing Behavior Models
-
Debugging a Behavior Model - Matching Triggers and Alarm Transitions - Examples of Matching Triggers and Transitions -
This section presents a number of examples of triggers and transitions that do and do not match.
A trigger named highLoad with the subobject system.0 and the node hp124 would prompt the following transitions:
The highLoad trigger would not prompt the following transition:
A trigger named lowSpace with the subobject $ANY, the node hp124, and the property includeMe (which is contained in hp124's property group) would prompt the following transitions:
The lowSpace trigger would not prompt the following transitions:
The trigger and transition fail the property rule.
The trigger and transition fail the node rule.
A trigger named lowSpace with the subobject $NULL, the node $ANY, and the property NO_PROP would prompt the following transitions:
The lowSpace trigger would not prompt the following transitions:
The trigger and transition fail the subobject rule.
The trigger and transition fail the subobject rule.
Previous: Rules for Matching | Next: Auditing Behavior Models |
Please send comments or corrections to Information Development | This file was last updated on 10 October © 2002 |