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().