Transition properties

For each FSM transition, the following properties can be set:
Table 1. FSM Transition Properties
Property Database table and column Description
Event Type FSM_TRANSITION. EVENT_TYPE_ID The type of event that can cause the state transition. It refers to a record in the EVENT_TYPE table.
Current State FSM_TRANSITION. OBJ_CUR_STATE The state an object can be in before this transition can apply. The state is referenced by name, such as, S_PTMapped.
Note: When the current and target states are NULL, the transition action is called in response to an event and no state change occurs. These transitions are known as null-state transitions.
Target State FSM_TRANSITION. OBJ_TAR_STATE The state an object is put into if all conditions are met and the transition is applied. The target state is referenced by name, such as, S_PTRelated.
Object Filter FSM_TRANSITION. OBJ_FILTER An SQL condition that is appended to the FSM object selector template to identify the objects that are subject to the transition.
Context values from the event can be referenced in the object filter condition by using the following notation: 
$Context{ContextName}
Where ContextName is what is stored in the CommonBaseEvent field: 
CommonBaseEvent.situationInformation.
contextDataElements[].name
The following example is an object filter: 
T.ID IN $Context{TRANSMISSION}
 AND T.TYPE='ACK'
Note:
  1. Quotation marks might sometimes be required around a $Context macro in an object filter. For example,
    '$Context{TXN_TYPE}'='ACK'
  2. Where multiple instances of the same type of context data might be in an event, such as a result of event aggregation, use the IN operator and not the = operator.
Action FSM_TRANSITION. FSM_ACTION The name of an action subflow to be called after the object transitions to the target state. By convention, action names begin with "A_". For example, A_CorrelatePT.

The result set from the FSM object selector is passed to the action in the environment.

An action must begin with the BeginAction subflow and end with the EndAction subflow. The action name is the name that is given to a label in the BeginAction subflow. This label name is promoted so that it can be set from the action subflow itself.
Override Selector Template FSM_TRANSITION. OVERRIDE_SELECTION This property is used to override the overall object selector template that is defined at the FSM level. It is used to tailor an object selector template for a particular transition. For example, to return some number of additional columns of data that is then available in the transition action.

All rules and conditions that apply to the FSM object selector template also apply to the transition override selector template.
Event Filter FSM_TRANSITION. EVENT_FILTER An ESQL Boolean expression that, if specified, must be true for the transition to be applied at all. For example, this expression might be used to define transitions that apply only to particular transaction types, when the overall FSM applies to more than one transaction type.

Event filters are evaluated independently of the object selector, but object filters are used to qualify it. For example, an object filter is used to more specifically identify the objects that the transition is applied to. If an event filter is present and evaluates to false, the object selector is not used to query the database. Nevertheless, all rules about how to specify an object filter also apply to event filters, including the mechanism to refer to event context data values in the condition.