Finite State Machine State Diagrams

The step from basic lifecycle diagrams to full FTM finite state machines (FSMs) should be fairly straight forward to follow since both diagrams are UML state diagrams. For more information about how to construct a valid FTM FSM model, see Designing applications.

The most significant differences are:

States are named based on the FTM naming convention of S_XXX.
Transition events are named based on the FTM naming convention of E_XXX.
Transition event names are enhanced to indicate in/out, txn/bat, and so on.
Event filters (Transition guard conditions) are fully defined in the FTM syntax.
Object filters are specified.
A number of error conditions and scenarios not previously discussed have been covered.

Each FSM must also specify an object selector template that is used to select objects for transition from the database. The data retrieved by the object selectors is available in actions called during state transitions. Inbound expected message transaction object selector template shows an object selector template for the inbound expected message object, and Scheduler task object selector template shows an object selector template for the scheduler task object

Figure 1. Inbound expected message transaction object selector template

SELECT ID,
       CID,
       SUBTYPE,
       CURRENCY,
       TRANSMISSION_ID,
       BATCH_ID,
       ISF_DATA
FROM $DBSchema.TXN_PAYMENT_V T
WHERE SUBTYPE='PAYMENT_ORIGINATION' AND STATUS=?

Figure 2. Scheduler task object selector template

SELECT ID,
       RESOURCE_REF PARTICIPANT_NAME,
       TASK_TIME
FROM $DBSchema.SCHEDULER_TASK_V  T
WHERE SUBTYPE = 'EXPECTED_MESSAGE_MONITOR' AND STATUS=?

Inbound expected message FSM shows the state diagram for the inbound expected message finite state machine, and Scheduler task FSM shows the state diagram for the scheduler task finite state machine.