Skip to main content

2025.11.6: Expiration of token

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 ahead
API 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.

2025.11.3: IDP endpoint for retrieving token

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.

2025.10.10: reference list change

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 zichtbaar
ZSDMSNotifications 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

2025.10.6: notification retries by Hangfire

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 herstart
ZCAThe 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.

2025.9.17: create your own Open BI Tokens

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/3252
CSVWhen modules Discover and Catalog are activated in RAB, a ClientId for that module is generated automatically
CSVWhen 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
ZGWThe 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

2025.9.8: Health check fix

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

2025.9.2: OneGround Community Edition ready

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.

2025.9.1: Health check and security fix

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
NRC, ZSDMS and DRCThe listeners of NRC, DRC and ZSDMS now support a health check.De health check is niet extern benaderbaar (voor bijvoorbeeld PRTG) omdat de listeners geen externe Api's hebben.
ZSDMSA previous security fix has led to problems in ZSDMS. This has been fixed.

2025.8.16: Hangfire queues separated

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
NRC, ZSDMSNRC and ZSDMS used the same Hangfire queue. They have been separated.Beheerders van Roxit kunnen nu events vanuit ZSDMS en NRC beter terugvinden

2025.8.13: Bugfix notifications

ComponentRelevance for consumers (English)Relevance for end users (Dutch)
NRCNotifications on channel documentacties where propagated without the original contents so that they could not be handled properly by receivers.Notificaties over het voltooien of afbreken uit ondertekensoftware kwamen niet goed aan bij de procesmodule zodat gebruikers geen waarschuwing kregen. Dit is nu opgelost.