Object history

The object history can be used to provide an audit trail. State and status changes of several objects can be logged with the help of database triggers that were designed for this task. By default, all these triggers are turned off. It is at the discretion of the customer to decide which of these triggers need to be turned on.

Some of these triggers are required to maintain the audit log tabs in the user interface. For example, the database trigger T_OB_HIS on the OBJ_BASE table makes a copy of operational data records before each state change.

Several options are available to define what is being logged:
  • Full transmission and transaction records.
  • Transmission and transaction records without LOB columns.
  • No transmission or transaction records, only object records (default).
  • Only certain types of object records; for example, no history for objects of type SERVICE_PARTICIPANT.

The triggers need to be tailored to log only the necessary minimum amount of information. Keeping too extensive, and maybe unnecessary, audit trails can have a negative effect on performance.

The tables that have database triggers that are available include the tables that are shown in the following list.
  • H_OBJ_BASE
  • H_OBJ_VALUE
  • H_ACTIVITY_BASE
  • H_FRAGMENT_BASE
  • H_TRANSMISSION_BASE
  • H_BATCH_BASE
  • H_TRANSACTION_BASE
  • H_TXN_PAYMENT_BASE
  • H_TXN_SECURITIES_BASE
  • H_SVC_PARTICIPANT_BASE

The documentation for the FTM data model for this version is provided in the entitled documentation fix pack for FTM. For more information about getting the fix pack, see FTM support links.