Object Lifecycle Analysis

From the list of FTM objects shown in the detailed sequence diagrams, the majority of the required finite state machines can re-use those in the FTM Generic Model. However, for this sample application the following objects require finite state machines to be designed and developed:
  • Inbound Transaction
  • Scheduler Task

The following figure shows the basic object lifecycle diagram for an inbound transaction in the sample application.

Figure 1. Inbound transaction object lifecycle diagram

The following figure shows the object lifecycle diagram of the Scheduler Task that represents the Payment Release Service. The Scheduler Task features two events. The Heartbeat Start event is issued once, when the sample application starts up. This will be used to initialize the Payment Release Service. The Heartbeat event happens every minute and will be used to run the Payment Release Service functionality when it is scheduled to occur.

Figure 2. Scheduler task lifecycle diagram

Scheduler Task Configuration

The Payment Release Service in this sample application has two responsibilities: to change the current business day (Service Participant's processing date) and to release payments. To achieve these two activities, the Scheduler Task has one Calendar Group associated with it. Within this Calendar Group are two Schedule Entries, one to change the business day and one to release payments. The time at which these activities occur at are held in the Schedule Entry's OPEN_TIME field. Furthermore, the Schedule Entry can target specific days of the week by setting MON_FLAG, TUES_FLAG, etc to either 'Y' or 'N'. For demonstration purposes, both Schedule Entries have all the 'days of the week' flags set to 'Y', including Saturday and Sunday.