Skip to main content

2026.4.2: UI problems in ZCA solved

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZCAIn the new UI for ZCA (task applications and ZSDMS), the plus button for adding ZSDMS case type configurations was greyed out, preventing new entries from being created. This has been resolved. Additionally, the sorting of the synchronisation overview now consistently shows the most recent entries at the top.In de nieuwe ZCA-interface (taakapplicaties en ZSDMS) was de plusknop voor het aanmaken van ZSDMS-zaaktypeconfiguraties niet meer beschikbaar. Dit is opgelost. Daarnaast worden in het synchronisatieoverzicht de meest recente items nu weer altijd bovenaan weergegeven.
DRCFetching all documents of an organization without any filtering caused errors for organizations with a large number of documents. The underlying database queries have been improved to reduce the frequency of these errors.API calls to retrieve all documents for an organization without filter parameters are now more reliable for organizations with large document volumes, as the underlying database queries have been optimized.Het ophalen van alle documenten van een organisatie zonder filtering leidde bij organisaties met veel documenten tot fouten. De onderliggende databasequery's zijn verbeterd, waardoor deze fouten minder vaak zouden moeten optreden.

2026.3.18: Various fixes

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCOn all DRC operations the audittrail 'New' and 'Old' value are the same except for lock and unlock. This has been fixed.The audittrail for DRC operations now correctly shows the old and new values, which improves traceability of changes.De audittrail voor DRC operaties toont nu correct de oude en nieuwe waardes, wat de traceerbaarheid van wijzigingen verbetert.
DRCA recent fix to enforce unique document identification (identificatie) inadvertently prevented any updates to documents that shared the same identification number as another document. This has been corrected.Client applications can now correctly PATCH or PUT documents that before the previous fix shared an identificatie with other documents, as long as the versie is different, which was previously blocked.Het was onterecht niet mogelijk om een document te wijzigen als een ander document met hetzelfde nummer bestond (maar met een ander versienummer). Dit is hersteld.

2026.3.15: Document Identification unique

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCThe 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.
ZRCThe 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
NRCFiltering 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.
GeneralThe 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

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
GeneralRedis 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.
GeneralThis 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

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZRCAllow object as value for zaakobject. objectIdentificatie. overigeDataThe 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.
NRCsubscription zaken with criterium DRNIt 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

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCBug fix: Latest EnkelvoudigInformatieObject Versie becomes null in rare cases
ZSDMSEndpoint Transfer migrated from CSV to ZSDMS_LISTENER
DRCBug fix: 409 http status code (locked)

2026.2.5: NRC: monitor unhealthy receiver endpoints

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
NRC ListenerIn 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 LegacyLog level for health check failures from ERROR to WARNING

2026.1.21: Secret restricted

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZCASecurity 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.
ZTCGET on Besluittype returned null for attribute 'vastgelegdIn' (incorrect). Now it returns []
DRCA delete on enkelvoudiginformatieobject returned sometimes a 500 error. This has been solved
DRCA post of enkelvoudiginformatieobject without bestandsnaam resulted in a 500-error (incorrect). This has been solved.
Number generatorThe 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

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZCAThe 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.
ZCASubscriptions could not be removed anymore. This has been solvedAbonnementen konden niet meer worden verwijderd. Dit probleem is opgelost.
BRCUpdating a besluit of a deprecated Besluittype was not possible. This has been solvedHet is nu mogelijk besluiten van een besluittype dat een einddatum vóór vandaag heeft, aan te passen.
DRCThere 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

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCTwo-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 LISTENERAfter 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.