actually executed. The history of an executed task includes time of execu- tion, the set of devices over which it was executed, its rollback status and other details which are generally regarded as audit details. In CMS, the audit details of selected tasks are as in Figure 11.23. The screen in Figure 11.23 exhibits a one-to-many relationship between a defined task and the set of instances of executions of that task. Start and finish times are shown, success or failure of the task execution on each relevant device, and so on. In the example shown, there is only one device called "suresh" associated with the task "test". The task execution instance shown in the last or most recent execution of the task "test". 11.2.15.2 Executing a Single Task Once a task is defined with a set of attributes and values assigned to them, it can be executed on one or more devices. The devices to be configured are defined by a device list but can also be selected individually before executing the task. Whether the latter is possible depends upon how the task was defined. Device lists comprise devices which are selected based on some criteria. It is neces- sary that device attributes must be configured before a task can be executed since 11 Configuration Management A Execute Task Execute Task Task Name SystemGroupConfiguration List Of Devices Device Attributes Devices Property Value advrouter Device N advrouter alexanderl amithkumara Commu public anantharaman Snmp Ve appin-server araman aravind Property aravindhan Value autotest-server Update Search for Devices Search Cancel Figure 11.24 Specifying devices on which a task will act. devices are the locus of task execution. Selection of devices on which a task can be executed is shown in Figure 11.24. The attributes of a selected device are shown in the right pane and device attributes can be added and modified in the lower right pane. 11.2.15.3 Executing Tasks as Templates As with "normal tasks", the devices that are to be configured by template tasks can also be defined under a device l