Multiple applications and versions

The FTM data model provides the ability to deploy multiple application models into a single FTM database instance. This allows the following benefits:

Separation of implementation
Ability to incrementally deploy business function to lower the risk, impact, or both, to existing business function

FTM achieves this separation by using an APPLICATION table. All operational and configuration data is associated with an entry in the APPLICATION table.

FTM application flows have a configurable attribute that allows you to specify the name of the application to run.

In addition to multiple application support, FTM also supports dual deployment of different versions of the same application. All configuration data is associated with a specific version of an application. Operational data, such as transmissions, batches, and transactions, is associated with an application only.

FTM application flows have a configurable attribute that allows you to specify the version of the application to run. Version information on the flows is optional. If no version is specified, the flows pick the most appropriate version of the application.

If an application version is specified, that version is run. If an application version is not specified, EFFECTIVE_DATETIME is used to identify the most appropriate version. The version loaded is the one with the most recent effective date that is not in the future.