|Bookshelf Home | Contents | Index | PDF|
Audit Trail creates a history of the changes that have been made to data in Siebel applications. An audit trail is a record showing who has accessed an item, which operation was performed, when it was performed, and how the value was changed. Therefore, it is useful for maintaining security, examining the history of a particular record, documenting modifications for future analysis, and record keeping. Audit Trail logs information without requiring any interaction with, or input from, your users.
Audit Trail can be used for a variety of purposes. In a simple example, a call center uses an audit trail to track the status change of a service request, who changed it and when. Audit trail capabilities can also be used to track the time needed to change the state of an item, such as a service request from open to closed. A calculation of the time difference can help the call center manager measure and improve service quality. Audit trail can also be used to reproduce a record at a given point in time to maintain regulatory compliance. This is done by looking at the audit trail records of changes and the current state of the record.
NOTE: For any audit trail deployment, the combination of the number of fields audited, and the number of audit records created by a given business process, has performance implications. Auditing a large number of fields on a business component, or auditing fields in a large number of business components, may produce unacceptable performance that is counter to the overall business requirement.
Audit trail works for replication and synchronization. For Siebel Remote and Siebel Replication users making changes to records, Audit Trail records successfully committed transactions and also transactions that did not get synchronized to the server because of conflicts.
|Applications Administration Guide|