2.2.2.1. action

Entity: action

An action is a task that a party must perform in response to one or more events. An action is often used in combination with a signal entity.

Example usage

The example below shows some actions related to the life event turning 18 (‘18 jaar worden’). It is possible to relate more actions to one event. The attribute actionType defines the kind of action(s) needed. The codelist AFDACT contains all available action types. If a party wants to define a custom action, he can use code ‘99’ and enter his own description (for example ‘Buy a cake’ / ‘Taart kopen’).

{
"signal": [{
	"entityType": "event", 
	"signalType": "01", 
	"partyRef": ["alexappelhof21"],
	"lifeEventType": "10",
	"lifeEventDescription": "18 jaar worden",
	"action": [{
		"entityType": "default",
		"actionType": "01",
		"actionDescription": "DigiD aanvragen",
		"priority": 1,
		"actionExplanation": "Als je 18 jaar wordt heb je een DigiD nodig",
		"url": "http://digid.nl"
	},
	{
		"entityType": "default",
		"actionType": "02",
		"actionDescription": "Zorgverzekering afsluiten",
		"priority": 1,
		"actionExplanation": "Als je 18 jaar wordt heb je een eigen zorgverzekering nodig",
		"url": "http://independer.nl"
	},
	{
		"entityType": "default",
		"actionType": "99",
		"actionDescription": "Taart kopen",
		"priority": 2
	}]
}]}

Entity types

There are no entity types within the action entity. Since this entity was added to AFD 2.0 only, there is no corresponding entity in AFD 1.0. More documentation on the use of SIVI AFS is available in chapter Where to find elements of SIVI AFS