User Guide › Service Level Management › Contracts › Audit Trail Tab › Contract Life cycle Audit Trail Report

Contract Life cycle Audit Trail Report

Audit trail report activities can be at the contract or version level. The following table shows the activities per level.

For example, when a contract's start date is set to a future date, the status is changed by the system from pending to effective on that date.

• An effective contract's status is changed from effective to not effective by the system. In this case, the user name is the system. Dates and times of automatic changes are according to effective dates (converted to user time zone) and not the actual time of changing the status by the system. For example, if a contract has an effective date of July 15, 2005 00:00 and the system changed the status on July 15, 00:10, the time displayed in the audit trail displays the time set as Effective.
• For Commit activities, the description is taken from the justification the user entered when committing the contract. (If no justification was entered, the description remains empty).
• Date and time is indicated in user time zone.

Exported contracts are exported with their audit trail reports. In full exports, users are exported with the Contract Audit Trail “as is”. Only the contract and related entities, and user names in the Contract Audit Trail are exported as is, and the user IDs are exported as Unknown (user ID = 0).

When importing a contract, it is imported with its audit trail.