State Models and Concepts
Each state model is owned by a concept. One concept can own multiple state models, but has only one main state model. The main state model can call the other state models.
Each state model begins with one start state and ends with one or more end states. Between the start and end states you can add simple, composite, and concurrent states as needed, connected by transitions. You can also add a Call State Model node to call another state model from within a state model.
Main State Model Inheritance
Each concept is allowed at most one main state model. However, a concept can inherit its main state model. At runtime, TIBCO BusinessEvents searches for a main state machine, starting with the concept instance. If it does not find one, it moves up the inheritance chain until it finds a main state machine. It creates an instance of the first main state machine it locates.
At runtime, if TIBCO BusinessEvents cannot locate a main state machine for the concept instance or for any concepts higher in the inheritance chain, it does not create an instance of any state machine for the concept instance.
A concept’s state machines can call any state machine that belongs to an ancestor of the concept. The state machine of a concept cannot call the state machine of a concept that is lower in the inheritance chain.
Call State Model
State model inheritance is used when you call another state model from within a state model: you can specify whether the call is an implicit or explicit call. See Call State Machine Resource.