2026.3.15: Document Identification unique

March 27, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
DRC	The combination of identificatie, versie, and owner for a document is now correctly enforced as unique. The previous implementation incorrectly used bronorganisatie instead of owner, which could lead to duplicate document numbers for a single owner. The business rules for handling document identification on POST and PATCH/PUT requests have also been corrected to align with this change.	Client applications may receive error responses if they attempt to create or update documents with non-unique identificatie and versie combinations for the same owner.	Het is nu niet neer mogelijk om hetzelfde documentnummer twee maal op te voeren.
ZRC	The database schema has been updated to correctly support complex objects for zaakobject. objectIdentificatie. overigeData. The old column has been removed and the new one (added in the previous release) now is correctly named.	Relevant for apps that rely on database exports like Data Export
NRC	Filtering on kenmerk_bron in GET requests for cases is now case-insensitive, ensuring more consistent and predictable filter results.	This improves the usability of the case filtering functionality, as queries will now return expected results regardless of casing.
General	The Hangfire retry page, which was broken, has been repaired.			Beheerders kunnen nu weer achtergrondtaken correct monitoren en beheren.

2026.3.10: Redis and ADFS improvements

March 22, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
General	Redis currently occupies one worker on its own (waste of resources while the load is low). Solution: create an own instance that can be hosted with other apps within the same worker.	This change is an internal optimization and has no direct impact on consumers.
General	This fix eliminates unnecessary IDP Legacy token introspection calls for ADFS-authenticated requests, improving performance while maintaining full backward compatibility for IDP Legacy-authenticated requests.	This improves performance for ADFS-authenticated requests.

2026.3.5: Bug fixes

March 16, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
ZRC	Allow object as value for zaakobject. objectIdentificatie. overigeData	The objectIdentificatie. overigeData field for a zaakobject with objectType "overige" now accepts any valid JSON object as a value, not just a string. This aligns with the ZGW specification. Existing string values remain valid and supported.
NRC	subscription zaken with criterium DRN	It is now possible to filter NRC subscriptions for the zaken channel based on the bron of a kenmerk. A new filter kenmerk_bron has been added. If this filter is provided in the subscription, notifications will only be sent for zaken that contain a kenmerk with a matching bron. This is useful for scenarios like filtering for a DSO verzoeknummer.

2026.3.2: Bug fixes

March 8, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
DRC	Bug fix: Latest EnkelvoudigInformatieObject Versie becomes null in rare cases
ZSDMS	Endpoint Transfer migrated from CSV to ZSDMS_LISTENER
DRC	Bug fix: 409 http status code (locked)

2026.2.5: NRC: monitor unhealthy receiver endpoints

February 11, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
NRC Listener	In the Hangfire dashboard for outgoing notifications a new page is added with unhealthy endpoints.			In het dashboard kun je zien welke endpoints (al dan niet tijdelijk) onbereikbaar zijn. Te bereiken via ZCA -> Beheer -> NRC Jobs -> Unhealthy endpoints
IDP Legacy	Log level for health check failures from ERROR to WARNING

2026.1.21: Secret restricted

January 28, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
ZCA	Security improvements: the visibility of the secret in taakapplicaties has been restricted to just after creation or rotation. The JWT copy function has been removed.		Het secret kan nu alleen vlak na het creeren of roteren ervan gekopieerd worden. Bovendien moet bij het roteren een reden opgegeven worden. U dient dus vanaf nu het secret direct op een veilige plaats op te slaan. Mocht u het kwijtraken, dan moet u het secret roteren (een nieuwe maken). De functie om een JWT te genereren is verwijderd. In plaats daarvan kan uw software bij IDP zelf een JWT opvragen. Deze maatregelen maken het moeilijker om ongewenste toegang tot OneGround te krijgen.
ZTC	GET on Besluittype returned null for attribute 'vastgelegdIn' (incorrect). Now it returns []
DRC	A delete on enkelvoudiginformatieobject returned sometimes a 500 error. This has been solved
DRC	A post of enkelvoudiginformatieobject without bestandsnaam resulted in a 500-error (incorrect). This has been solved.
Number generator	The number generator returned wrong case numbers if a case was created in the first hour of a new year. This has been resolved for new cases.		Als een zaak werd aangemaakt in het eerste uur van het nieuwe jaar werd de teller van de nummergenerator niet teruggezet naar 0. Hierdoor ging de nummering van daaropvolgende zaken door met weliswaar het juiste jaartal in het zaaknummer maar met een volgnummer gebaseerd op het laatste volgnummer van het jaar daarvoor. Dit is opgelost voor nieuwe gevallen.

2026.1.15: special client id for support tooling and field 'reason' in the JWT function

January 19, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
ZCA	The client id for support now has a preferred name 'support tooling'. Use of the name Postman is deprecated. This client id can only be created or modified by admins. Also, when creating a JWT token, the new field 'reason' has to be filled in by the user. In this way it will be clear to customers when support actions are taking place and why.			De client-ID voor support heeft nu de voorkeursnaam 'support tooling'. Deze client-ID kan alleen door beheerders worden aangemaakt of gewijzigd. Het gebruik van de naam 'Postman' wordt vanaf nu afgeraden. Bij het aanmaken van een JWT-token moet de gebruiker bovendien het nieuwe veld 'reden' invullen. Zo is het voor klanten duidelijker wanneer en waarom supportacties plaatsvinden.
ZCA	Subscriptions could not be removed anymore. This has been solved			Abonnementen konden niet meer worden verwijderd. Dit probleem is opgelost.
BRC	Updating a besluit of a deprecated Besluittype was not possible. This has been solved		Het is nu mogelijk besluiten van een besluittype dat een einddatum vóór vandaag heeft, aan te passen.
DRC	There were errors when deleting document objects (=relationship to zaak or besluit), possibly because of simultaneous API delete calls on enkelvoudiginformatieobjects and objectinformatieobjects. The delete queries within the delete operation for objectinformatieobjects now have been separated in order to prevent concurrency problems.

2026.1.7: stricter check on language code 'taal' of informatieobject

January 13, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
DRC	Two-letter and capital language codes were accepted in attribute 'taal' whereas the standard allows only three lowercase letters. Now the taal is checked on valid ISO-values. In case of often occuring deviating values like NLD or nl, it is replaced by nld.
NRC LISTENER	After the last retry on sending a notitifcation to an non-responding endpoint an Error was logged. Because of this the logs were full of errors of external systems while the NRC was functioning correctly. For this reason the error level now is reduced to Warning.

2026.1.5: improvements on notifications and document deletion

January 10, 2026

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
NRC Listener	The retry mechanism for sending notifications has been improved with separate retry queues in Hangfire. Unresponding endpoints now are temporarily marked as unhealthy to prevent unnecessary loads of retry notifications.
DRC	There were errors when deleting documents, possibly because of simultaneous API delete calls on enkelvoudiginformatieobjects and objectinformatieobjects. The delete queries within the delete operation for enkelvoudiginformatieobjects now have been separated in order to prevent concurrency problems.

2025.12.10: Notifications via Hangfire

December 22, 2025

Component	Summary (english)	Relevance for consumers (English)	Relevance for end users (Dutch)	Relevance for system administration (Dutch)
ZRC, BRC, DRC Listener	Rabbitmq has been replaced by Hangfire as a mechanism for dipatching notifications from BRC and ZRC to DRC. DRC Listener now has an endpoint for receiving notifications.	It is now easier to combine OneGround registrations with other registrations. For example, a OneGround BRC can be combined with an external DRC and vice versa.		Systeembeheerders kunnen nu notificaties van BRC en ZRC bekijken en beheren in het Hangfire-dashboard.
CSV	Swagger endpoints for CSV have been completed, especially those for ZSDMS
All ZGW API's	There was a possibility in the test environment to access data of all tenants with one ClientId. This possibility has been removed.
All ZGW API's	The Postman test is now integrated in the pipeline and runs automatically.
ZTC, CSV	When a catalogue is added automatically, user contact data are automatically retrieved from RAB and stored in the Catalogue in the ZTC.
ZRC, DRC	When a date/time was returned, for example a registration date of the case, it was returned without timezone indication. ISO-8601 says: "If the time is in UTC, add a Z directly after the time without a space". Now the Z has been added.	This might be a breaking change
ZCA	The lay out of the Custom Headers section in Application client has been improved
All ZGW	Health checks on ZGW API's did not follow the Roxit standard and created errors for monitoring tools. Now, an authenticated health endpoint has been added.	Monitoring tools now can use the authenticated endpoint
ZCA	The edit-possibilities of subscriptions have been removed. The reason is that filter options were not shown, and the result of editing was therefore unpredictable. Also automatically insertion of subscriptions by CSV makes manual editing superfluous. A tooltip was added showing the filter values of each subscription.