2025.8.9: Caching of catalog types improved
| Component | Relevance for consumers (English) | Relevance for end users (Dutch) |
|---|---|---|
| ZTC | When deprecating a version (by setting eindeGeldigheid) and then creating a new version of an IOT or BT that is already connected to case types based on the value of Omschrijving, the new version was not immediately usable in cases, because of caching. This problem has been solved. | Soms was een nieuwe versie van een besluittype of informatieobjecttype niet direct beschikbaar bij het aanmaken van een zaak. Dit is opgelost. |
| ZRC | Retries on expands are now with a very short interval en limit retry count to improve performance. | |
| NRC | In OneGround unlimited, ZGW services publish events to a RabbitMQ message queue. Notification handlers then process these events and forward them to NRC consumer endpoints. This approach creates a tight coupling with RabbitMQ that other NRC's than OneGround do not support. It now also is possible to enable OneGround services to send notifications directly to arbitrary NRC Api's via an HTTP client. |