Working with State Modeler

A state model consists of nodes (states and Call State Model nodes) and transitions.

You can search for nodes or transitions using a specialized search feature. See Searching State Model Entities.

Nodes
 A state model begins with one start state and ends with one or more end states. Between the start and end states you can add any number of other nodes: simple, composite, and concurrent states. Each state can have optional entry and exit actions.
Transitions  
You connect the nodes with transitions, which can optionally depend on rules. You can define a transition that has no rule. This is called a lambda transition. If you configure a rule for a transition, the transition does not occur until the rule executes successfully.

Functions

The State Modeler includes its own set of functions, which are located in the Standard function registry under Instance > StateMachine. See Functions in TIBCO BusinessEvents Architect’s Guide and TIBCO BusinessEvents Developer’s Guide (and tooltips provided in TIBCO BusinessEvents Studio).

Note:  Like all concepts, concepts with state machines aren't automatically deleted when their main state machines reach the end state. You must explicitly delete concept instances in your rules, using Instance.deleteInstance().
  • Adding State Models
    You can add complex states that allow you to nest nodes and transitions within them. You can also add Call State Model nodes, which allow you to call other state models.
  • Removing and Changing State Model Ownership
    A state model must be owned by a concept in order to execute. Depending on your ontology and rule logic, it may be possible to change the owner of a state model to another concept.
  • Outlining a State Model
    Build a outline for the state model by adding the nodes you need and connecting them with transitions. Then you can fill in the details by configuring each node and transition.
  • Guidelines for Adding Transitions
    You can connect one state to more than one other state, and you can connect to one state from more than one other state.
  • State Model Preferences
    The State Model preferences are available from Windows > Preferences > TIBCO BusinessEvents > Diagram > State Model.
  • Configuring Nodes
    Configure the state model and individual state properties to define action for each state or call for the state model.
  • Configuring Transitions
    All transition configuration is done using tabs in the Properties view for the transition.
  • Defining Timeouts
    You can define timeouts for the overall state model and each of its states.
  • Controling the Start of a State Machine
    By default, main state machines start when their associated concept instance is asserted. You can also configure TIBCO BusinessEvents not to start a concept's main state machine immediately after the concept is asserted.
  • Searching State Model Entities
    State models can become quite complex. You can search for specific states or transitions using the State Modeler Search Entity feature. It enables you to search either state nodes or transition edges in any one search.
  • State Model Resource Reference
    State model resources are used to model the life cycle of a concept instance. Within a state model resource you configure states and transitions and calls to other state models.
  • State Resource Reference
    Simple, composite, and concurrent states, as well as regions within concurrent states have the full set of tabs. Start and end states, and Call State Model resources have a subset as noted.
  • Call State Model Resource Reference
    The Call State Model resource allows you to call any state machine that is at the same level or higher in the inheritance chain.