Open JanBrek opened 1 month ago
Jan presented this image as the desired UX for setting your messaging preferences:
There are 4 important aspects:
Draft idea:
MeldingType
that holds the configurable messaging preferences (point 1, 2 and 4 above).GET /api/v1/meldingtypen
[
{
"categorieNaam": "Meldingen over uw zaken",
"naam": "Besluiten",
"code": "besluit", # This code needs to come from the notify component.
"mogelijkeKanaalCodes": [
"post", # These codes will be in the Referentielijsten API as possible channels.
"email",
"sms"
],
"verplichteKanaalCodes": ["post"]
},
{
"categorieNaam": "Meldingen over uw zaken",
"naam": "Statuswijzigingen",
"code": "status",
"mogelijkeKanaalCodes": [
"email",
"sms"
],
"verplichteKanaalCodes": ["email"]
},
{
"categorieNaam": "Nieuwsberichten",
"naam": "Updates van uw gemeente",
"code": "nieuws",
"mogelijkeKanaalCodes": [
"email"
],
"verplichteKanaalCodes": []
}
]
DigitaalAdres
resource: meldingsvoorkeuren
. This is an array that holds all the codes from the notify component.{
"verstrektDoorBetrokkene": {
"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f"
},
"verstrektDoorPartij": {
"uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f"
},
"adres": "johndoe@example.com",
"soortDigitaalAdres": "email",
"omschrijving": "Persoonlijke e-mailadres",
"meldingsvoorkeuren": [ # New :)
"besluit",
"status"
]
}
@JanBrek could you validate this? I denormalized category to make it simple. On client level, for UI purposes, you can simply group on the categorieNaam
instead of having another resource for meldingsCategorieen
or so.
Thema / Theme
Contactgevens API
Omschrijving / Description
From Den Haag the request is to have more fine grained contact configuration.
(Pre-discussed with Joeri B)
Toegevoegde waarde / Added value
No response
Aanvullende opmerkingen / Additional context
No response