In this tab, you can add auditing properties to the object, in order to track its event history.

To be filled in if the changes of the object must be kept in a tracking table; see Audit.

• Audit enabled: Check this box in order to be able to generate records of changes to the object available in the Object[General] tab. In the attribute details, you can specify which attributes are affected and which changes are to be audited.
  
• Filter: An SQL expression for limiting the triggering of tracking to special conditions.
  For example, old.STATUS_CODE = 'VALIDATE' so that a change is only tracked if the STATUS_CODE column has the value "VALIDATE" prior to the change.
  

  In some cases, the SQL syntax to be used may be different depending on the target database type.

  For example, for the creation of an audit on the costCenter object that is only triggered if the description equals TEST:

  • with Oracle^® or PostgreSQL^®, the filter criterion will be: new.description = 'TEST'
  • with SQL Server^®, the filter criterion must be: EXISTS (select * from csfi_costcenter c join inserted i on i.id = c.id where i.description ='TEST')
  
  
• Table: To specify the record storage table. It is simplest to use the default table.

If you wish to use another one (i.e. for reasons having to do with volume), the new table will have to be created in the database and added to the values list. In this case, a Java^® class will have to be created in order to access the data in the [Viewing records] function.

• Identifiers: The tracked information is always at least the name of the attribute and the old and new values. These additional identifiers will allow you to view the values of other attributes of the changed line, and are intended to filter/group data when displaying records.
  Example: code and name of the object.

Multi-time zone management

In an international context, if you wish to audit fields such as "date" or "date-time," we recommend that you enable auditing on the "temporalContextStore" identifier.