Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions changelog/2026/03-27-release-2026.3.15.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
slug: "2026.3.15"
title: "2026.3.15: Document Identification unique"
---

| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| DRC | The 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. | |
| ZRC | The 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 | | |
| NRC | Filtering 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. | | |
| General | The Hangfire retry page, which was broken, has been repaired. | | | Beheerders kunnen nu weer achtergrondtaken correct monitoren en beheren. |
Loading