sk XML obtained using the getDeviceConfiguration method and applies the task to a set of devices. 11.2.4.4 Task DTD An XML document can optionally have its grammar specified by a Document Type Definition (DTD). A document that is required to be of some particular type is then validated against the DTD corresponding to that type. Accordingly, there is a "Task" DTD that specifies the format of XML code which is used to define any task so that any task that generated using an API or from a client conforms to this DTD. The task DTD has several tags of which <ConfigTask> tag is at the highest level. Table 11.2 explains the parameters of this tag. 11.2.4.5 Creating Task Templates Assuming that a task has been defined to change the system property of a device, when defining the task, the required value for the system property is specified. Once Table 11.2 Parameters for ConfigTask DTD tag. Tag name Description TaskName The name of the task to which the record applies IsTemplate Specifies whether or not the task is a template task IsNewTask Specifies whether or not the task is new. If "true", the task will be created, and if "false", the existing task will be overwritten IsOverWrite Specifies whether the existing task should be overwritten if there is a task with the same name IsSequential Specifies whether the devices should be configured in a sequence or whether order does not matter RollbackDocument The name of the rollback task is specified here, so that this task will be executed if the rollback type is set to rollbackDocument RollbackNeeded This parameter is used to specify whether or not rollback is needed. If rollback is set to true, either the current configuration or rollbackDocument is executed CombinedTask This parameter is used to specify whether or not the task is a combined task. In other words, the tag specifies whether the task contains sub-tasks Persistence This parameter is used to specify whether or not the created task must be stored. By default, this is set to "true" and all of the tasks will be sto