Audit - Specific issues
The sections describe the impact of several changes you can make in the audit settings.
The impact of a change depends on the specific situation. The situations that are described arise if changes in the audit settings are converted to run time while not all users did leave LN. Therefore, some users create audit trails based on the old configuration, while users that start afterwards create audit trails based on the new configuration.
Changes in the profiles
This table summarizes the impact of the changes for a particular table in a company:
| Change Impact of changes for a particular table in a company | Consequence |
|---|---|
| Impact of changes for adding a table. | Users that still use the old settings do not audit some transactions. |
| Remove a table. | Some transactions that must not be audited with the new settings are still audited by users that use the old settings. |
| Change the audit type for a table or field. | Some transactions are audited according to the old settings, while other transactions are audited according to the new settings. |
| Add or remove a field. | After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Users with the old settings can be forced to restart LN. |
- If you switch field-specific auditing for a table on or off, and this results in a different number of fields to be audited. Then the impact of this change is the same as adding or removing a field.
- Not every change in the audit settings results in other settings at run time. If you convert the new settings to run time, the net result of the changes for the entire configuration might be zero.
Changes in the maximum file size of the sequence files
If the maximum file size of the sequence files is changed and converted to run time, the new file size is immediately effective. This goes for users with the old settings, and for users with the new settings. If the file size was enlarged, the current file grows until this new size. If the file size was diminished, and the current file already exceeds this size, a new file is created the next time a transaction is logged.