2026.10.9: Upgrade to .NET 10
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZGW | Changed: the source code now runs on .NET 10. |
2026.10.6: ZRC 1.7 fields parameter, DRC 1.0 removed and filename fix
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZRC | Added: the fields parameter on the _zoek operation (API v1.7). | It is now possible to add a fields parameter to a _zoek request and so expand related resources and return only the fields you need, which reduces the size of the response. For example, fields can request only identificatie together with the zaakinformatieobjecten, their informatieobject and the omschrijving of the informatieobjecttype, to see which document types are valid for a zaak. | ||
| DRC | Removed: version 1.0 of the DRC API standard is no longer supported. | Version 1.0 of the standard is no longer supported. The remaining supported versions are 1.1, 1.5 and 1.7, so consumers still using 1.0 have to switch to one of these. | ||
| DRC | Fixed: retrieving a document whose filename contains a question mark no longer returns an error. | Fixed: retrieving a document whose filename contains a question mark no longer returns an error. | Opgelost: documenten met een vraagteken in de bestandsnaam konden niet worden opgehaald en gaven een foutmelding. Deze documenten kunnen nu gewoon worden geopend. |
2026.9.17: Security updates and ZRC duplicate-activity fix
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| All modules | Fixed: security updates have been applied across all ZGW components. | |||
| ZRC | Fixed: a zaakobject whose objectIdentificatie.overigeData.activiteiten contains two identical entries can now be saved. | Fixed: updating a zaakobject whose objectIdentificatie.overigeData.activiteiten contains two identical entries no longer returns a 500 error. The request is now processed and the zaakobject is stored as sent. | Opgelost: een verzoek met twee dezelfde activiteiten kon voorheen niet worden opgeslagen en leverde een onjuist zaakobject op. Zo'n verzoek wordt nu correct verwerkt. |
2026.9.15: DRC 1.7 complete and AutoMapper to Mapster migration finished
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| All modules | Fixed: internal object-to-object mapping has been migrated from AutoMapper to Mapster in all remaining modules | Not relevant — this is an internal implementation change with no impact on public API behavior, request/response formats, or contracts. | Niet relevant — er verandert niets aan de functionaliteit of de gebruikersinterface. | |
| DRC | Fixed: DRC API version 1.7 is now fully implemented | Fixed: it is now possible to add an expand parameter to a search action in the DRC and to specify which fields should be included in the response. This allows software developers to significantly reduce the size of response messages. With this change, version 1.7 of the ZGW standard for the DRC is now fully implemented. | In de DRC is er nu de mogelijkheid om een expand toe te voegen aan een zoekactie en kunnen de gewenste velden in het antwoord gespecificeerd worden. Hierdoor is het mogelijk voor software ontwikkelaars om de grootte van responseberichten enorm te verkleinen. Met deze wijziging is versie 1.7 van de ZGW-standaard voor de DRC nu geheel geïmplementeerd. |
2026.9.3: ZRC rol contactpersoon validation
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZRC | POST /rollen (API v1.5) now rejects a contactpersoonRol object without naam with a 400 Bad Request instead of an unhandled 500 | A rol request whose contactpersoonRol omits naam or sends it as null now returns 400 with an invalidParams entry naming contactpersoonRol.naam. An empty string is still accepted and returns 201 unchanged. |
2026.8.27: ZCA publication-restriction control
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZCA | Added a checkbox on the applicatie (client) screen to set alleenIsGereedVoorPublicatie directly | Bij het beheren van een taakapplicatie is nu met een selectievakje in te stellen dat deze applicatie alleen documenten (enkelvoudige informatieobjecten) mag lezen waarvan de eigenschap isGereedVoorPublicatie in het DRC op true staat. |
2026.8.26: ZRC expand casing fix
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZRC | Fixed incorrect key casing in expand responses (v1.5) | GET /zaken/{uuid}?expand=... responses previously named three keys with a leading capital instead of camelCase: betrokkeneIdentificatie on embedded rollen, and url/uuid on embedded zaakobjecten. All three now match the VNG standard's casing. The plain /rollen and /zaakobjecten endpoints were already correct and are unchanged. | ||
| ZRC | Migrated internal object mapping from AutoMapper to Mapster. |
2026.8.23: ZSDMS transfer logging
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| ZSDMS | ZSDMS transfer (overdragen zaak) now emits a traceable log trail at INFO level — receipt, saga progress, the reply, and the reason for any refusal or failure — all tagged with the same case identifier, on both the external and internal routes. | Voor het overdragen van een zaak (ZSDMS transfer) is er nu een volledig logspoor op INFO-niveau: ontvangst, tussenstappen van de saga, het verzonden antwoord en de reden bij een weigering of technische fout. Elke regel draagt hetzelfde veld ZaakIdentificatie, waarop in Kibana gefilterd kan worden — zo is één overdracht van begin tot eind te herleiden zonder de broncode te raadplegen. Voorheen werden deze regels alleen op Debug-niveau gelogd en waren dus niet zichtbaar. | ||
| DRC/ZTC | Migrated internal object mapping from AutoMapper to Mapster |
2026.8.18: DRC 1.7 additions
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| DRC | DRC updated with standard version 1.6 and 1.7 additions | Field tonenAanInitiator added (default: false). trefwoorden added to the PATCH operation. Verzenddatum no longer required for outgoing documents. Authorization for documents with alleenIsGereedVoorPublicatie = true added (works together with AC standard 1.1.0). By default, responses still use DRC 1.5; to test the 1.7 behavior, send the 1.7 API version header. DRC 1.7 will become the default once all 1.7 changes are implemented. | ||
| NRC/BRC | Migrated internal object mapping from AutoMapper to Mapster |
2026.8.3 AC standard 1.1.0
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
|---|---|---|---|---|
| AC | AC standard support updated from 1.0.0 to 1.1.0: added field alleenIsGereedVoorPublicatie | New optional boolean field alleenIsGereedVoorPublicatie (default: false) on the AC standard. If set to true, the associated application may only read documents for which isGereedVoorPublicatie is true. Not yet functional: DRC will be adjusted in an upcoming release to actually enforce this restriction. |