Taak aangemaakt

Notifies the respective party (e.g., a citizen or an organization) that the new task was assigned to them.

Notification

Example of JSON schema:

{
  "actie": "create",
  "kanaal": "objecten",
  "resource": "object",
  "kenmerken": {
    "objectType": "https://..."
  },
  "hoofdObject": "https://...",
  "resourceUrl": "https://...",
  "aanmaakdatum": "2000-01-01T10:00:00.000Z"
}

Environment variables

Required to be set:

ZGW_WHITELIST_TASKASSIGNED_IDS

ZGW_VARIABLE_OBJECTTYPE_TASKOBJECTTYPE_UUID

NOTIFY_TEMPLATEID_EMAIL_TASKASSIGNED

NOTIFY_TEMPLATEID_SMS_TASKASSIGNED

5.2.5.3. Requirements

• The initial notification has:

  • Action: Create ("create")

  • Channel: Objects ("objecten")

  • Resource: Object ("object")

• The GUID from object type URI ("objectType") in the initial notification has to be whitelisted or "*" wildcard used (to accept all object types) in respective whitelist environment variable. This step will distinguish for which object type the notification is desired (e.g., tasks, messages, etc.)

• The task status ("status") from record.data nested object is set to open ("open")

• The task identification type ("type") from record.data.identificatie is set to: -- private person ("bsn") -- or company ("kvk")

• The case type identifier ("zaaktypeIdentificatie") has to be whitelisted or "*" wildcard used (to accept all case types) in respective whitelist environment variable

• The notification indication property ("informeren") in case type is set to true

• All URIs are valid, source data complete, and JWT token or API keys correct

The notification will be processed and sent!

Otherwise, user will get a meaningful API feedback from OMC application explaining what exactly is missing.

5.2.5.4. Template placeholders

Required placeholders names in the Notify NL template:

((klant.voornaam))

((klant.voorvoegselAchternaam))

((klant.achternaam))

((taak.verloopdatum))

((taak.heeft_verloopdatum))

((taak.record.data.title))

((zaak.identificatie))

((zaak.omschrijving))