Finite state machine state diagrams
The step from basic lifecycle diagrams to full FTM finite state machines (FSMs) should be fairly straightforward to follow since both diagrams are UML state diagrams. For more information about how to construct a valid FTM FSM model, see Designing applications.
- 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 payment batch object selector template shows an object selector template for the inbound payment batch object. Inbound payment transaction object selector template shows an object selector template for the inbound payment transaction object and Outbound domestic CT batch object selector template shows an object selector template for the outbound domestic CT batch object.
Inbound payment batch FSM shows the state diagram for the inbound payment batch finite state machine, Inbound payment transaction FSM shows the state diagram for the inbound payment transaction finite state machine, and Outbound domestic CT batch FSM shows the diagram for the outbound domestic CT batch FSM.