<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="atom.xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://dev.oneground.nl/changelog</id>
    <title>OneGround ZGW API Changelog</title>
    <updated>2026-05-11T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://dev.oneground.nl/changelog"/>
    <subtitle>Latest releases and updates for OneGround ZGW API platform</subtitle>
    <icon>https://dev.oneground.nl/img/favicon.png</icon>
    <entry>
        <title type="html"><![CDATA[2026.5.9: Security and billing improvements]]></title>
        <id>https://dev.oneground.nl/changelog/2026.5.9</id>
        <link href="https://dev.oneground.nl/changelog/2026.5.9"/>
        <updated>2026-05-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                 | Relevance for consumers (English) | Relevance for end users (Dutch)                            | Relevance for system administration (Dutch)                                                                                             |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZRC</td><td>Audit trail now contains GET requests BSN</td><td></td><td>Zoekacties op basis van BSN worden gelogd in de audit log.</td><td></td></tr><tr><td>ZRC</td><td>HMAC key rotation support was implemented for encrypted BSN, including versioned key usage and migration tooling.</td><td></td><td></td><td>Beheerders kunnen sleutels gecontroleerd roteren met migratieondersteuning, wat security-beheer en operationele continuiteit verbetert.</td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.5.3: Audit trail optimization]]></title>
        <id>https://dev.oneground.nl/changelog/2026.5.3</id>
        <link href="https://dev.oneground.nl/changelog/2026.5.3"/>
        <updated>2026-05-07T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                | Relevance for consumers (English)                                                                                                                                                                                                                                                                                                    | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZGW</td><td>Audittrail optimizations for improved efficiency</td><td>The storage of the audit trail was optimized in order to decrease the enormous size of the audit trails. From now on changes are stored as delta's and snapshots (snapshots being created after 25 delta's.). Existing audit trails still are kept in the 'old' format. There is no change in the response on GET's of audit trails.</td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.4.13: BSN encrypted]]></title>
        <id>https://dev.oneground.nl/changelog/2026.4.13</id>
        <link href="https://dev.oneground.nl/changelog/2026.4.13"/>
        <updated>2026-04-16T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                 | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZRC</td><td>BSNs in database table <code>zaakrollen_natuurlijk_personen</code> are now stored encrypted.</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.4.2: UI problems in ZCA solved]]></title>
        <id>https://dev.oneground.nl/changelog/2026.4.2</id>
        <link href="https://dev.oneground.nl/changelog/2026.4.2"/>
        <updated>2026-04-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                                                                                                                                                      | Relevance for consumers (English)                                                                                                                                                                              | Relevance for end users (Dutch)                                                                                                                                                                                                                                             | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZCA</td><td>In 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.</td><td></td><td>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.</td><td></td></tr><tr><td>DRC</td><td>Fetching 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.</td><td>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.</td><td>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.</td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.3.18: Various fixes]]></title>
        <id>https://dev.oneground.nl/changelog/2026.3.18</id>
        <link href="https://dev.oneground.nl/changelog/2026.3.18"/>
        <updated>2026-03-30T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                                                  | Relevance for consumers (English)                                                                                                                                                                                 | Relevance for end users (Dutch)                                                                                                                                     | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>DRC</td><td>On all DRC operations the audittrail 'New' and 'Old' value are the same except for lock and unlock. This has been fixed.</td><td>The audittrail for DRC operations now correctly shows the old and new values, which improves traceability of changes.</td><td>De audittrail voor DRC operaties toont nu correct de oude en nieuwe waardes, wat de traceerbaarheid van wijzigingen verbetert.</td><td></td></tr><tr><td>DRC</td><td>A recent fix to enforce unique document identification (<code>identificatie</code>) inadvertently prevented any updates to documents that shared the same identification number as another document. This has been corrected.</td><td>Client applications can now correctly <code>PATCH</code> or <code>PUT</code> documents that before the previous fix shared an <code>identificatie</code> with other documents, as long as the <code>versie</code> is different, which was previously blocked.</td><td>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.</td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.3.15: Document Identification unique]]></title>
        <id>https://dev.oneground.nl/changelog/2026.3.15</id>
        <link href="https://dev.oneground.nl/changelog/2026.3.15"/>
        <updated>2026-03-27T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                                                                                                                                                                                                                                                    | Relevance for consumers (English)                                                                                                                                             | Relevance for end users (Dutch)                                                  | Relevance for system administration (Dutch)                              |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>DRC</td><td>The combination of <code>identificatie</code>, <code>versie</code>, and <code>owner</code> for a document is now correctly enforced as unique. The previous implementation incorrectly used <code>bronorganisatie</code> instead of <code>owner</code>, which could lead to duplicate document numbers for a single owner. The business rules for handling document identification on <code>POST</code> and <code>PATCH</code>/<code>PUT</code> requests have also been corrected to align with this change.</td><td>Client applications may receive error responses if they attempt to create or update documents with non-unique <code>identificatie</code> and <code>versie</code> combinations for the same <code>owner</code>.</td><td>Het is nu niet neer mogelijk om hetzelfde documentnummer twee maal op te voeren.</td><td></td></tr><tr><td>ZRC</td><td>The database schema has been updated to correctly support complex objects for <code>zaakobject. objectIdentificatie. overigeData</code>. The old column has been removed and the new one (added in the previous release) now is correctly named.</td><td>Relevant for apps that rely on database exports like Data Export</td><td></td><td></td></tr><tr><td>NRC</td><td>Filtering on <code>kenmerk_bron</code> in <code>GET</code> requests for cases is now case-insensitive, ensuring more consistent and predictable filter results.</td><td>This improves the usability of the case filtering functionality, as queries will now return expected results regardless of casing.</td><td></td><td></td></tr><tr><td>General</td><td>The Hangfire retry page, which was broken, has been repaired.</td><td></td><td></td><td>Beheerders kunnen nu weer achtergrondtaken correct monitoren en beheren.</td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.3.10: Redis and ADFS improvements]]></title>
        <id>https://dev.oneground.nl/changelog/2026.3.10</id>
        <link href="https://dev.oneground.nl/changelog/2026.3.10"/>
        <updated>2026-03-22T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                                                | Relevance for consumers (English)                                              | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>General</td><td>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.</td><td>This change is an internal optimization and has no direct impact on consumers.</td><td></td><td></td></tr><tr><td>General</td><td>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.</td><td>This improves performance for ADFS-authenticated requests.</td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.3.5: Bug fixes]]></title>
        <id>https://dev.oneground.nl/changelog/2026.3.5</id>
        <link href="https://dev.oneground.nl/changelog/2026.3.5"/>
        <updated>2026-03-16T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                      | Relevance for consumers (English)                                                                                                                                                                                                                                                                                                                                        | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZRC</td><td>Allow object as value for zaakobject. objectIdentificatie. overigeData</td><td>The <code>objectIdentificatie. overigeData</code> field for a <code>zaakobject</code> with <code>objectType</code> "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.</td><td></td><td></td></tr><tr><td>NRC</td><td>subscription zaken with criterium DRN</td><td>It is now possible to filter NRC subscriptions for the <code>zaken</code> channel based on the <code>bron</code> of a <code>kenmerk</code>. A new filter <code>kenmerk_bron</code> has been added. If this filter is provided in the subscription, notifications will only be sent for <code>zaken</code> that contain a <code>kenmerk</code> with a matching <code>bron</code>. This is useful for scenarios like filtering for a DSO verzoeknummer.</td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.3.2: Bug fixes]]></title>
        <id>https://dev.oneground.nl/changelog/2026.3.2</id>
        <link href="https://dev.oneground.nl/changelog/2026.3.2"/>
        <updated>2026-03-08T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                             | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>DRC</td><td>Bug fix: Latest EnkelvoudigInformatieObject Versie becomes null in rare cases</td><td></td><td></td><td></td></tr><tr><td>ZSDMS</td><td>Endpoint Transfer migrated from CSV to ZSDMS_LISTENER</td><td></td><td></td><td></td></tr><tr><td>DRC</td><td>Bug fix: 409 http status code (locked)</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.2.5: NRC: monitor unhealthy receiver endpoints]]></title>
        <id>https://dev.oneground.nl/changelog/2026.2.5</id>
        <link href="https://dev.oneground.nl/changelog/2026.2.5"/>
        <updated>2026-02-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component    | Summary (english)                                                                                  | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch)                                                                                                              |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>NRC Listener</td><td>In the Hangfire dashboard for outgoing notifications a new page is added with unhealthy endpoints.</td><td></td><td></td><td>In het dashboard kun je zien welke endpoints (al dan niet tijdelijk) onbereikbaar zijn. Te bereiken via ZCA -&gt; Beheer -&gt; NRC Jobs -&gt; Unhealthy endpoints</td></tr><tr><td>IDP Legacy</td><td>Log level for health check failures from ERROR to WARNING</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.1.21: Secret restricted]]></title>
        <id>https://dev.oneground.nl/changelog/2026.1.21</id>
        <link href="https://dev.oneground.nl/changelog/2026.1.21"/>
        <updated>2026-01-28T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component        | Summary (english)                                                                                                                                                      | Relevance for consumers (English) | Relevance for end users (Dutch)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZCA</td><td>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.</td><td></td><td>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 <a href="https://dev.oneground.nl/docs/general/authentication" target="_blank" rel="noopener noreferrer" class="">IDP</a> zelf een JWT opvragen. Deze maatregelen maken het moeilijker om ongewenste toegang tot OneGround te krijgen.</td><td></td></tr><tr><td>ZTC</td><td>GET on Besluittype returned null for attribute 'vastgelegdIn' (incorrect). Now it returns []</td><td></td><td></td><td></td></tr><tr><td>DRC</td><td>A delete on enkelvoudiginformatieobject returned sometimes a 500 error. This has been solved</td><td></td><td></td><td></td></tr><tr><td>DRC</td><td>A post of enkelvoudiginformatieobject without bestandsnaam resulted in a 500-error (incorrect). This has been solved.</td><td></td><td></td><td></td></tr><tr><td>Number generator</td><td>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.</td><td></td><td>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.</td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.1.15: special client id for support tooling and field 'reason' in the JWT function]]></title>
        <id>https://dev.oneground.nl/changelog/2026.1.15</id>
        <link href="https://dev.oneground.nl/changelog/2026.1.15"/>
        <updated>2026-01-19T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                                                                                                                                                                                        | Relevance for consumers (English) | Relevance for end users (Dutch)                                                                       | Relevance for system administration (Dutch)                                                                                                                                                                                                                                                                                                                                                    |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZCA</td><td>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.</td><td></td><td></td><td>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.</td></tr><tr><td>ZCA</td><td>Subscriptions could not be removed anymore. This has been solved</td><td></td><td></td><td>Abonnementen konden niet meer worden verwijderd. Dit probleem is opgelost.</td></tr><tr><td>BRC</td><td>Updating a besluit of a deprecated Besluittype was not possible. This has been solved</td><td></td><td>Het is nu mogelijk besluiten van een besluittype dat een einddatum vóór vandaag heeft, aan te passen.</td><td></td></tr><tr><td>DRC</td><td>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.</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.1.7: stricter check on language code 'taal' of informatieobject]]></title>
        <id>https://dev.oneground.nl/changelog/2026.1.7</id>
        <link href="https://dev.oneground.nl/changelog/2026.1.7"/>
        <updated>2026-01-13T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component    | Summary (english)                                                                                                                                                                                                                                                       | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>DRC</td><td>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.</td><td></td><td></td><td></td></tr><tr><td>NRC LISTENER</td><td>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.</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2026.1.5: improvements on notifications and document deletion]]></title>
        <id>https://dev.oneground.nl/changelog/2026.1.5</id>
        <link href="https://dev.oneground.nl/changelog/2026.1.5"/>
        <updated>2026-01-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component    | Summary (english)                                                                                                                                                                                                                                                                                           | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>NRC Listener</td><td>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.</td><td></td><td></td><td></td></tr><tr><td>DRC</td><td>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.</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.12.10: Notifications via Hangfire]]></title>
        <id>https://dev.oneground.nl/changelog/2025.12.10</id>
        <link href="https://dev.oneground.nl/changelog/2025.12.10"/>
        <updated>2025-12-22T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component              | Summary (english)                                                                                                                                                                                                                                                                                                              | Relevance for consumers (English)                                                                                                                               | Relevance for end users (Dutch) | Relevance for system administration (Dutch)                                                            |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZRC, BRC, DRC Listener</td><td>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.</td><td>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.</td><td></td><td>Systeembeheerders kunnen nu notificaties van BRC en ZRC bekijken en beheren in het Hangfire-dashboard.</td></tr><tr><td>CSV</td><td>Swagger endpoints for CSV have been completed, especially those for ZSDMS</td><td></td><td></td><td></td></tr><tr><td>All ZGW API's</td><td>There was a possibility in the test environment to access data of all tenants with one ClientId. This possibility has been removed.</td><td></td><td></td><td></td></tr><tr><td>All ZGW API's</td><td>The <a href="https://github.com/OneGround/ZGW-APIs-postman-tests/blob/main/ZGW%20business%20rules.postman_collection.json" target="_blank" rel="noopener noreferrer" class="">Postman test</a> is now integrated in the pipeline and runs automatically.</td><td></td><td></td><td></td></tr><tr><td>ZTC, CSV</td><td>When a catalogue is added automatically, user contact data are automatically retrieved from RAB and stored in the Catalogue in the ZTC.</td><td></td><td></td><td></td></tr><tr><td>ZRC, DRC</td><td>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.</td><td>This might be a breaking change</td><td></td><td></td></tr><tr><td>ZCA</td><td>The lay out of the Custom Headers section in Application client has been improved</td><td></td><td></td><td></td></tr><tr><td>All ZGW</td><td>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.</td><td>Monitoring tools now can use the authenticated endpoint</td><td></td><td></td></tr><tr><td>ZCA</td><td>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.</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.11.6: Expiration of token]]></title>
        <id>https://dev.oneground.nl/changelog/2025.11.6</id>
        <link href="https://dev.oneground.nl/changelog/2025.11.6"/>
        <updated>2025-11-18T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component   | Summary (english)                                       | Relevance for consumers (English)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Relevance for end users (Dutch) | Relevance for system administration (Dutch)                                                                                                                                                                                                                                                                                                                                                                                                            |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>IDP</td><td>Lifetime of bearer tokens now is restricted to 24 hours</td><td>Self generated bearer tokens should have an expiration time less than 24 hours ahead</td><td></td><td></td></tr><tr><td>API Gateway</td><td>Possibilty to add version headers on incoming requests</td><td>In 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-<em>, x-custom-</em></td><td></td><td></td></tr><tr><td>ZCA</td><td>ClientId ZSDMS not editable</td><td></td><td></td><td>De door het systeem gegenereerde ZSDMS-ClientId was bewerkbaar in ZCA-taakapplicaties. Het bewerken is nu niet meer mogelijk.</td></tr><tr><td>Reflist</td><td>Revert removal of P29</td><td></td><td></td><td>Vorige 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.</td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.11.3: IDP endpoint for retrieving token]]></title>
        <id>https://dev.oneground.nl/changelog/2025.11.3</id>
        <link href="https://dev.oneground.nl/changelog/2025.11.3"/>
        <updated>2025-11-11T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                    | Relevance for consumers (English)                                                          | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>IDP</td><td>Endpoint for retrieving bearer token</td><td>Instead of generating a bearer token by the application, it can now be requested from IDP.</td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.10.10: reference list change]]></title>
        <id>https://dev.oneground.nl/changelog/2025.10.10</id>
        <link href="https://dev.oneground.nl/changelog/2025.10.10"/>
        <updated>2025-11-03T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component      | Summary (english)                                                                                                 | Relevance for consumers (English) | Relevance for end users (Dutch)                                                                                                                                                                                                                                                                                         | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>Reference list</td><td>Changes in result types of provincial selection lists</td><td></td><td>Resultaattype 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'.</td><td></td></tr><tr><td>ZCA</td><td>The label 'modified' in page 'Application Client' was incorrect and is replaced by 'last action'</td><td></td><td>Op pagina 'Taakapplicatie' stond in de kop van de lijst 'laatste wijziging'. Dit was niet correct en is nu vervangen door 'laatste actie'</td><td></td></tr><tr><td>ZCA</td><td>The button 'case types' in page 'Application Client' had disappeared and is now visible again.</td><td></td><td>Op pagina 'Taakapplicatie' was de knop 'zaaktypen' in sommige gevallen verdwenen. Deze is weer zichtbaar</td><td></td></tr><tr><td>ZSDMS</td><td>Notifications for ZSDMS were transported via RabbitMQ. Now they are sent as regular notifications via a web hook.</td><td></td><td>Het signaal om ZSDMS-close te starten wordt nu via een andere technische component verstuurd</td><td></td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.10.6: notification retries by Hangfire]]></title>
        <id>https://dev.oneground.nl/changelog/2025.10.6</id>
        <link href="https://dev.oneground.nl/changelog/2025.10.6"/>
        <updated>2025-10-02T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component    | Summary (english)                                                                                | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch)                                                                               |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>NRC_Listener</td><td>Notification retries previously were handled by Rabbit MQ. Rabbit MQ now is replaced by Hangfire</td><td></td><td></td><td>Niet gelukte notificaties kunnen nu terug gevonden worden in Hangfire (ZCA menu item Beheer -&gt; NRC Jobs) en daar herstart</td></tr><tr><td>ZCA</td><td>The checkbox for synchronization with PMA in the subscriptions panel has been removed.</td><td></td><td></td><td>De chckbox "subscribe from PMA" is verwijderd omdat de werking en bedoeling onduidelijk waren.</td></tr></tbody></table>]]></content>
    </entry>
    <entry>
        <title type="html"><![CDATA[2025.9.17: create your own Open BI Tokens]]></title>
        <id>https://dev.oneground.nl/changelog/2025.9.17</id>
        <link href="https://dev.oneground.nl/changelog/2025.9.17"/>
        <updated>2025-09-26T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[| Component | Summary (english)                                                                                                                                                                 | Relevance for consumers (English) | Relevance for end users (Dutch)                                                                                                                                                                            | Relevance for system administration (Dutch) |]]></summary>
        <content type="html"><![CDATA[<table><thead><tr><th>Component</th><th>Summary (english)</th><th>Relevance for consumers (English)</th><th>Relevance for end users (Dutch)</th><th>Relevance for system administration (Dutch)</th></tr></thead><tbody><tr><td>ZCA</td><td>A function was added to create ClientId's and secrets for OpenBI</td><td></td><td>U kunt nu zelf toegangsgegevens tot OpenBI genereren als u de module OpenBI heeft afgenomen. Voor details over hoe het werkt zie <a href="https://community.rxmission.nl/t/hoe-richt-ik-openbi-in-voor-gebruik/3252" target="_blank" rel="noopener noreferrer" class="">https://community.rxmission.nl/t/hoe-richt-ik-openbi-in-voor-gebruik/3252</a></td><td></td></tr><tr><td>CSV</td><td>When modules Discover and Catalog are activated in RAB, a ClientId for that module is generated automatically</td><td></td><td></td><td></td></tr><tr><td>CSV</td><td>When 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 ZTC</td><td></td><td></td><td></td></tr><tr><td>ZGW</td><td>The 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</td><td></td><td></td><td></td></tr></tbody></table>]]></content>
    </entry>
</feed>