https://dev.oneground.nl/changelog OneGround ZGW API Changelog 2026-04-16T00:00:00.000Z https://github.com/jpmonette/feed Latest releases and updates for OneGround ZGW API platform https://dev.oneground.nl/img/favicon.png <![CDATA[2026.4.13: BSN encrypted]]> https://dev.oneground.nl/changelog/2026.4.13 2026-04-16T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)ZRCBSNs in database table zaakrollen_natuurlijk_personen are now stored encrypted.]]> <![CDATA[2026.4.2: UI problems in ZCA solved]]> https://dev.oneground.nl/changelog/2026.4.2 2026-04-10T00:00:00.000Z 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.]]> <![CDATA[2026.3.18: Various fixes]]> https://dev.oneground.nl/changelog/2026.3.18 2026-03-30T00:00:00.000Z 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.]]> <![CDATA[2026.3.15: Document Identification unique]]> https://dev.oneground.nl/changelog/2026.3.15 2026-03-27T00:00:00.000Z 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 ExportNRCFiltering 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.]]> <![CDATA[2026.3.10: Redis and ADFS improvements]]> https://dev.oneground.nl/changelog/2026.3.10 2026-03-22T00:00:00.000Z 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.]]> <![CDATA[2026.3.5: Bug fixes]]> https://dev.oneground.nl/changelog/2026.3.5 2026-03-16T00:00:00.000Z 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.]]> <![CDATA[2026.3.2: Bug fixes]]> https://dev.oneground.nl/changelog/2026.3.2 2026-03-08T00:00:00.000Z 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 casesZSDMSEndpoint Transfer migrated from CSV to ZSDMS_LISTENERDRCBug fix: 409 http status code (locked)]]> <![CDATA[2026.2.5: NRC: monitor unhealthy receiver endpoints]]> https://dev.oneground.nl/changelog/2026.2.5 2026-02-11T00:00:00.000Z 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 endpointsIDP LegacyLog level for health check failures from ERROR to WARNING]]> <![CDATA[2026.1.21: Secret restricted]]> https://dev.oneground.nl/changelog/2026.1.21 2026-01-28T00:00:00.000Z 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 solvedDRCA 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.]]> <![CDATA[2026.1.15: special client id for support tooling and field 'reason' in the JWT function]]> https://dev.oneground.nl/changelog/2026.1.15 2026-01-19T00:00:00.000Z 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.]]> <![CDATA[2026.1.7: stricter check on language code 'taal' of informatieobject]]> https://dev.oneground.nl/changelog/2026.1.7 2026-01-13T00:00:00.000Z 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.]]> <![CDATA[2026.1.5: improvements on notifications and document deletion]]> https://dev.oneground.nl/changelog/2026.1.5 2026-01-10T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)NRC ListenerThe 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.DRCThere 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.]]> <![CDATA[2025.12.10: Notifications via Hangfire]]> https://dev.oneground.nl/changelog/2025.12.10 2025-12-22T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)ZRC, BRC, DRC ListenerRabbitmq 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.CSVSwagger endpoints for CSV have been completed, especially those for ZSDMSAll ZGW API'sThere was a possibility in the test environment to access data of all tenants with one ClientId. This possibility has been removed.All ZGW API'sThe Postman test is now integrated in the pipeline and runs automatically.ZTC, CSVWhen a catalogue is added automatically, user contact data are automatically retrieved from RAB and stored in the Catalogue in the ZTC.ZRC, DRCWhen 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 changeZCAThe lay out of the Custom Headers section in Application client has been improvedAll ZGWHealth 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 endpointZCAThe 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.]]> <![CDATA[2025.11.6: Expiration of token]]> https://dev.oneground.nl/changelog/2025.11.6 2025-11-18T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)IDPLifetime of bearer tokens now is restricted to 24 hoursSelf generated bearer tokens should have an expiration time less than 24 hours aheadAPI GatewayPossibilty to add version headers on incoming requestsIn order to deal with the breaking changes in ZTC 1.2 and 1.3 we created the possibility to add Api-version headers on the Api Gateway for consumers. It is relevant for consumer that assume an older version of the ZTC but do not send a Api-version header. The following HTTP version headers are possible: accept, accept-crs, accept-language, api-version, content-crs, content-type, if-match, if-none-match, prefer, x-audit-toelichting, x-nlx-request-application-id, x-nlx-request-subject-id, x-nlx-request-user-id, x-client-, x-custom-ZCAClientId ZSDMS not editableDe door het systeem gegenereerde ZSDMS-ClientId was bewerkbaar in ZCA-taakapplicaties. Het bewerken is nu niet meer mogelijk.ReflistRevert removal of P29Vorige week is een aantal wijzigingen aan de referentielijsten gedaan. P29 is daarbij verwijderd bij procestype verzoeken behandelen omdat de rubriek van P29 in de provinciale selectielijst toezicht en handhaving is wat niet overeen lijkt te komen met verzoeken behandelen. Het blijkt nu echter dat in de ZTC Omgevingswet 1.8 P29 wel degelijk gekoppeld is aan dit proces. Daarom is P29 weer toegevoegd aan procestype verzoeken behandelen.]]> <![CDATA[2025.11.3: IDP endpoint for retrieving token]]> https://dev.oneground.nl/changelog/2025.11.3 2025-11-11T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)IDPEndpoint for retrieving bearer tokenInstead of generating a bearer token by the application, it can now be requested from IDP.]]> <![CDATA[2025.10.10: reference list change]]> https://dev.oneground.nl/changelog/2025.10.10 2025-11-03T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)Reference listChanges in result types of provincial selection listsResultaattype P46-ingewilligd was gerelateerd aan procestype 'toezicht en handhaving' en is nu gerelateerd aan procestype 'verzoeken behandelen'. P29-ingewilligd is verwijderd bij proces 'toezicht en handhaving'. Resultaattypen P1-Afgebroken en P22-Verleend zijn toegevoegd aan procestype 'Evaluatie uitvoeren'.ZCAThe label 'modified' in page 'Application Client' was incorrect and is replaced by 'last action'Op pagina 'Taakapplicatie' stond in de kop van de lijst 'laatste wijziging'. Dit was niet correct en is nu vervangen door 'laatste actie'ZCAThe button 'case types' in page 'Application Client' had disappeared and is now visible again.Op pagina 'Taakapplicatie' was de knop 'zaaktypen' in sommige gevallen verdwenen. Deze is weer zichtbaarZSDMSNotifications for ZSDMS were transported via RabbitMQ. Now they are sent as regular notifications via a web hook.Het signaal om ZSDMS-close te starten wordt nu via een andere technische component verstuurd]]> <![CDATA[2025.10.6: notification retries by Hangfire]]> https://dev.oneground.nl/changelog/2025.10.6 2025-10-02T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)NRC_ListenerNotification retries previously were handled by Rabbit MQ. Rabbit MQ now is replaced by HangfireNiet gelukte notificaties kunnen nu terug gevonden worden in Hangfire (ZCA menu item Beheer -> NRC Jobs) en daar herstartZCAThe checkbox for synchronization with PMA in the subscriptions panel has been removed.De chckbox "subscribe from PMA" is verwijderd omdat de werking en bedoeling onduidelijk waren.]]> <![CDATA[2025.9.17: create your own Open BI Tokens]]> https://dev.oneground.nl/changelog/2025.9.17 2025-09-26T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)ZCAA function was added to create ClientId's and secrets for OpenBIU kunt nu zelf toegangsgegevens tot OpenBI genereren als u de module OpenBI heeft afgenomen. Voor details over hoe het werkt zie https://community.rxmission.nl/t/hoe-richt-ik-openbi-in-voor-gebruik/3252CSVWhen modules Discover and Catalog are activated in RAB, a ClientId for that module is generated automaticallyCSVWhen OneGround for Rx.open, Moor, Rx.Base or Rx.Mission is activated in RAB, a catalogue for the correspondent domain is generated automatically in the ZTCZGWThe size of log files has been decreased. The new configuration creates a new log file each day, limits each individual file to 100 MB, and keeps a maximum of 3 recent log files]]> <![CDATA[2025.9.8: Health check fix]]> https://dev.oneground.nl/changelog/2025.9.8 2025-09-17T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)NRC, ZSDMS and DRCA problem with the previous version of the health check has been fixed.ZRCCreate/update ZaakObject now validates against new zaakObjectType from ZTC 1.3]]> <![CDATA[2025.9.2: OneGround Community Edition ready]]> https://dev.oneground.nl/changelog/2025.9.2 2025-09-05T00:00:00.000Z ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)AllOneGround Community Edition (Open Source) already supported OAuth2. Support of self signed tokens now has been added, so that it can be used by existing common ground clients.]]>