Fields

If this date is entered, only those data whose last modification or creation date is later than or equal to it are viewed in the inquiry.

Except if there is a memo that specifies its value, the default value for this date is defined by the DATEDEBDFTuserparameter.

If this date is entered, only those data whose last modification or creation date is earlier than or equal to it are viewed in the inquiry.

Except if there is a memo that specifies its value, the default value for this date is defined by the DATEFINDFTuserparameter.

It is used to define a filter on the audited table. If this field is entered, only those lines relating to the table in question are viewed.

It is used to only view the modifications relating to the fields complying with the naming template.

Warning, when a field is sized, it is specified in the audit table in the form FIELD(INDEX), and the first index in the form FIELD(0). If a filter is requested for the FIELD value, nothing will appear: either FIELD(0) has to be entered to se the first index, or FIELD(*), to see them all.

When this box is checked, a line appears for each traced field (the lines relating to the modification of the same record can be identified by an identical sequence number).

If it is not checked, there is one line per modification (on which at least one of the fields is traced), but the detail of the field modifications is not displayed.

It is used to define a filter on the user code. If this field is assigned, only those modifications made by the corresponding user appear in the inquiry.

It is used to define a filter on the user login code. If this field is entered, only those modific ations made by the users connected under the corresponding login code appear in the inquiry.

To view only those modifications made directly to the database without going through the software, the External login code needs only to be selected (by right click).

It is used to filter the lines to be presented on the event at the origin of the audit. In the absence of any values, all the lines are presented, but if a filtering is required, only 3 values are possible:

• INSERT (to view all the creations)
• UPDATE (to view all the modifications)
• DELETE (to view all the deletions)

Only the first character (I,U,D) needs to be entered for the entry to be completed in this field.

Unique chronological number assigned upon releasing of the audited event. A single chrono is assigned by record at the origin of the audit : if several fields can be logged, an identical chrono number is found on all the corresponding lines.

It corresponds to the table in which the audited event took place.

It defines the system date on the data server at the moment of execution of the audited event.

It defines the system time on the data server at the moment of execution of the audited event.

It defines the type of audited event. There are three possible choices:

• INSERT defines a line creation. In this case, the field previous value is empty, and the new value fields contains the value of the field at the time of the creation.
• DELETE defines a line deletion. In this case, the field new value is empty, and the previous value fields contains the value of the field before the deletion.
• UPDATE defines a line modification. In this case, the previous value contains the value before modification, and the new value field contains the value of the field after modification.

It defines the key value of the record at the origin of the audit, when the key is composed of a single field. When it is composed of several fields, only the value of the first field is stored here.

The key identifying the record is defined in the Audit tab of the tables management. By default, it is the first key.

When the key of the record at the origin of the audit is composed of several fields, the value of the fields can be found here in the proper order from the second field, these fields being separated by the ~ character (tilde).

The key identifying the record is defined in the Audit tab of the tables management. By default, it is the first key.

It defines the user code (in the meaning of the software) that triggered the audited event.

If the event has been triggered outside of the software, this field is empty.

It corresponds to the system login of the user at the origin of the audited event. If the event has been triggered outside of the software, the login that appears here is External.

It defines the address (in the network meaning) of the user at the origin of the audited event. If this address cannot be determined, the field is entered with Unknown. This is namely the case for all the modifications performed outside of the software.

It defines the audited field in the form FIELD in case of a non-sized field, and FIELD(INDEX) if the field is sized.

In case of modification or deletion, the value of the field before the operation can be found here.

In case of modification or creation, the value of the field after the operation can be found here.

This status is used to find out if a Workflow has been requested on this audit. It can take the following values:

• None: The Workflow box is not checked in the audit parameterization for the corresponding table.
• To process: The Workflow box is checked, but no Workflow event of the Manual type based on the run thgrough of the audit table has processed a notification and updated this field.
• Processed: The Workflow box is checked, and a later notification processing took place.