Entity levels and versions

You must define each entity separately. However, more than one occurrence of the same entity can exist. FTM SWIFT uses levels to track the occurrences of an entity.

Every time you change an entity and activate those changes, FTM SWIFT generates a new level for the entity. For example, when you create an entity and put it into production for the first time, this entity is at level 1. Later, if you decide to change the entity, as soon as it enters the modification stage, it is at level 2. The level is incremented only when you change an entity after it was made active.

Each level also contains information about the exact life-cycle state of the entity. Table 1 lists the valid level life-cycle states for each entity type.

Table 1. Valid life-cycle states for a level
Configuration entities	Security entities
In process	In process
Committed	Committed
Approved	Approved
Deployed

You can further categorize these life-cycle states into the following level states:

Active: The entity is in production.
In process: The entity is under development.
History: The entity is no longer used.

Table 2 shows how the different life-cycle states fit into the appropriate level state.

Table 2. Level states and life-cycle states
Level state	Life-cycle states
Level state	Configuration entities	Security entities
Active	Deployed	Approved
In process	In process Committed Approved	In process Committed
History	Committed Approved Deployed	Committed Approved

When you change an FTM SWIFT entity and activate it, its level state changes from In process to Active. At the same time, the previously deployed entity that is being replaced changes its level state from Active to History. You can have only one active level of an FTM SWIFT entity, but you can have many levels that have the state History.