task details, so that entries are made in the TaskAudit and DeviceAudit tables only. Level 2 means to audit device, task and attribute details, so that entries are made in all three tables. When a device is configured with the auditing option set, the audit details are stored the database. These details can be accessed from the database using API methods. When a device is configured, audit details such as the name of the task, starting time of task execution, time of finish and the user who executed the task are logged in the database for audit purposes. This auditing information may accumulate in the database so that, eventually, older information need no longer be retained in the database. The "clean audit interval" parameter deletes information older than a specified time period, that is, it sets how often we start with a clean audit database. The default value of the "clean audit interval" is 1, so that audit details older than one day are deleted from the database. 11.2.4.7.2 Auditing: Custom Views Custom views are user-defined views that satisfy certain match criteria. Custom views can be used to limit or otherwise customise the information that is presented Table 11.3 Task level audit table. Value Description Execution ID This is the number which will be incremented sequentially for every task submission Username This stores the name of the user who has executed the task Taskname The name of the task which was executed is stored here Device list This is used to store the DeviceList names over which the task was executed. The DeviceList contains a set of devices which can be stored like a Task. The list of devices can be given as comma-separated values Data source This is used to store the data source for the task template, i.e. the template can get its input from Inventory, network element, etc. Execution time This is the time at which the task was submitted for execution OSS for Telecom Networks A Add Custom View Form Add Custom View Please enter the values for the properties given below to create Custom 