red. If it is desirable to execute the task on the fly without storing it, then this is set to "false" Version The task version Description A description of the task RollbackLevel The rollback level set for a particular task. It can be a task level, device level, etc. DeviceResult Specifies whether or not the result of configuration of a sub-task of a combined task must immedi- ately be sent to the clients. If "false", then the result is sent only upon completion of all sub-tasks of the combined task InterPacketDelay Sets delay between successive packets, when the task is submitted for execution Encoding The encoding which will be used to parse the task XML, such as ISO-8859-1, UTF-8, UTF-16, etc. 11 Configuration Management a task is created with particular parameters, the same task cannot be reused for another value. Template-based configuration allows for task reuse and allows vari- ation of only the system property value. The template takes input from the data source which forms the repository of input data. When the configuration template is executed, the values to be filled in the template are taken from the data source. The setTemplate method of the TaskGenerator API class specifies whether a con- figuration task or template must be created. If so, then the setTaskName method of TaskGenerator is used to set the name of the configuration template. The getTask method of TaskGenerator is used to create the task XML code and the task is then stored in this format. 11.2.4.6 Source of Data for Completing Tasks When a device is to be configured by a task, the parameter values to be assigned to the attributes must be supplied to the task before that task is executed. In the case of a template-based task, these data will be inputs to the parameterised placeholders of the template. The types of parameter that forms the data input to the templates are: Inventory Inputs: comprises data gathered from the network inventory database. NE Inputs: comprises data obtained by querying network elements for the values to be use