Skip to content

Commit 0ecd5d2

Browse files
Create 03-27-release-2026.3.15.md (#108)
1 parent 52241a4 commit 0ecd5d2

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
slug: "2026.3.15"
3+
title: "2026.3.15: Document Identification unique"
4+
---
5+
6+
| Component | Summary (english) | Relevance for consumers (English) | Relevance for end users (Dutch) | Relevance for system administration (Dutch) |
7+
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
8+
| 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. | |
9+
| 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 | | |
10+
| 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. | | |
11+
| General | The Hangfire retry page, which was broken, has been repaired. | | | Beheerders kunnen nu weer achtergrondtaken correct monitoren en beheren. |

0 commit comments

Comments
 (0)