3.16. taskStructure

General properties

The main characteristics of the taskStructure are the presence of the task entity, which groups general information about a task for, for example, inspection, appraisal or repair of damage. Therefore, claim and claim-related entities (party, policy) often occur within the taskStructure, but this is not mandatory.

Mandatory components

The table below contains all mandatory entities and attributes of the taskStructure. Please note: these are only the mandatory components; in this case only the presence of a task. In many functions and messages, the message will be more extensive, including claim and incident entities, and often a commonFunctional entity for meta-data. See later in this section for a more detailed example. More information about functions related to task is available in chapter Domain specific functions under Task.

See AFD 2.0 Online for the complete and up-to-date data catalog with all entities, entityTypes and attributes, associated with the taskStructure. More documentation on the use of SIVI AFS is available in chapter Where to find elements of SIVI AFS. A general description of AFD structures is provided in the introduction to AFD structures, while information on details of AFD structures is available in chapter Where to find details about AFD structures.

JSON example

Below is an example of a taskStructure, including details about the corresponding task. Note that at the top level within JSON, the taskStructure entity is not explicitly mentioned. In XML, the structure is always explicitly defined at the highest level as well.

{
	"commonFunctional": [ {
		"entityType": "default",
		"functionVariant": "update",
		"dataCatalogVersion": "34C"
	} ],
	"task": [ { 
		"entityType": "default",
		"desiredExecutionDate": "2023-03-01",
		"party": [ {
			"entityType": "principal",
			"porCompany": "A754"
		},
		{
			"entityType": "contractor",
			"firstName": "Bert",
			"surname": "Nieuwkoop"
		} ]
	} ]
}