Changes
- Updated CMIS-adapter to 1.1 featuring support CMIS 1.0 Webservice binding and various new configuration options.
- Added support for configurable Selectielijst years to retrieve specific years from the Selectielijst API (#689)
- Prevent error monitoring from logging special personal data (#696)
Bugfixes
- Accept comma separated in
EigenschapSpecificatie.waardenverzameling
(#686)
Documentation
- Added SPDX license headers and check.
- Added Docker storage hint to make sure users run the Docker containers on volumes with enough disk space.
Version 1.3.0 of Open Zaak introduces some new features, quality of life changes and fixes bugs discovered in 1.2.0.
There is no 1.2.1 bugfix release. Upgrading from 1.2.0 to 1.3.0 requires no manual intervention.
What's new?
- Added experimental support for CMIS backends for the Documenten API, as an alternative to Open Zaak database + filesystem. See the documentation for more details.
- Added a feature flag to allow unpublished
*Typen
to be used. This should only be used in Proof-of-concept environments, as it violates the VNG standard. - Added a number of CLI commands for initial Open Zaak setup following installation. See the documentation for more details.
- Implemented extra
zaak_list
filters, added in 1.0.2 of the Zaken API standard maxVertrouwelijkheidaanduiding
betrokkene
betrokkeneType
omschrijvingGeneriek
natuurlijk persoon BSN
medewerker identificatie
- Implemented extra
Bugfixes and general QOL changes
- Positioned the Foundation for Public Code and checked Open Zaak against their standard/guidelines
- The documentation now includes a Public Code checklist
- Added Code of Conduct
- Added Governance documentation
- Fixed running tests with
--keepdb
option - Fixed the admin form for
Zaaktype-Informatieobjecttype
relation - Fixed importing a
Zaaktype-Informatieobjecttype
with aStatustype
relation - Improved documentation for deploying on Kubernetes
- Added English version of README
- Fixed configuration form for external services when the NLX directory has not been configured (yet)
- Fixed
BesluitType
create in the admin (#594) - Added and documented performance-profiling tooling for Open Zaak developers
- Fixed performance regression in
zaak_list
endpoint operation ⚡ - Fixed a crash on malformed UUIDs in endpoint URLs that expect a valid UUID 4 pattern
- Added the environment configuration reference to the published documentation
- Refactored notifications/selectielijst configuration to use the external services configuration
- Fixed
EigenschapSpecificatie.waardenverzameling
default value (empty list) (#611) - Fixed missing validation on (zaaktype, eigenschapnaam) uniqueness
- Added Slack invite link
- Relaxed Resultaat.afleidingswijze validation in the admin too (see also
6e38b865c
) - Improved "Contributing" section
New feature release and a set of bugfixes included.
Features
- Update admin layout version
- #507 -- use the original filename when downloading a document from the admin
- Reworked configuration of external APIs
- Added option to specify your NLX outway location and network
- Added the ability to enable/disable APIs offered by Open Zaak
- Added the option to configure external APIs, optionally selecting services from the NLX network.
- Added support for custom OAS urls. Note that you need to add them manually
in
zgw_consumers.Service
for existing APIs (you can do it in the admin).
Bugfixes
- Bumped a number of libraries to their latest security releases
- #511 -- fix saving of resultaattype if bewaartermijn is null
- #495 -- use correct page titles for api schemas per component
- #318 -- Fixed (BesluitType)Admin M2M relations so that they show content from the same catalogus only
- Fixed Document inhoud base64 validation
- Enabled pre-filling the informatieobjecttype in zaaktype-informatieobjecttype admin
- #532 -- fixed issue with
Resultaattype.omschrijving_generiek
not updating - #551 -- ensure client credentials are deleted when an
Applicatie
is deleted in in the admin - #543 -- fix error when trying to create a document in the admin
- Fixed creating a Zaaktype with partial
referentieProces
gegevensgroep - #553 -- made Eigenschap.specificatie required in admin
- #557 -- fix handling of
brondatumArchiefProcedure: null
- #558 -- fixed
ZaakBesluit
DELETE
calls - #556 -- fixed admin crash for resultaattype when the related zaaktype does not have a selectielijst procestype set
- #559 -- fixed deploying Open Zaak on a subpath (as opposed to on its own (sub)domain)
- #554 -- fixed admin crash when related informatieobjecttypen/besluiten are not available for a given zaak.
- #562 -- fixed nested
Eigenschap.specificatie
being ignored
Documentation
- Documentation minimal version of required development tooling
- #299 -- Fixed notification documentation generation
- Updated PR template
- #534 -- updated documentation links in the API specs
Bugfix release w/r to deployment and ADFS
- Added option to disable group sync in ADFS login. If the ADFS provider does not provide the group claim, this would otherwise reset the user groups you carefully configured.
- Updated single-server deployment to make sure the web-server can read and serve uploaded files through the Documenten API.
New feature release. Note that this is not yet an implementation of the 1.1.x API specs!
- Included playbooks for NLX deployment
- Added communication channels to the docs (i.e. - how to find/contact us!)
- Added ADFS support (i.e. you can now log in to the admin with ADFS)
- Fixed some deployment tooling
Improved support for integration with other APIs, most notably BAG/BRT APIs from the kadaster (see https://pdok.nl). This increases the usability of ZaakObject relations.
- Added api-test.nl badge - proves that Open Zaak is compliant with the API's voor zaakgericht werken standard
- Added small documentation improvements
- Updated notification setup instructions
- Added support for API authentication with a simple API key (such as BAG or BRT)
- Added support for URL transformation so that data-fetching is forced over NLX
Fixed infrastructure on single-server where Open Zaak and Open Notificaties run on the same machine.
Bugfixes and usability improvements
- Improve selectielijst-resultaten display in ResultaatType admin (#480)
- Improved production description
- Fixed file permissions for installation on single-server (#481)
Bugfixes from initial release
- Added version information to Docker image
- Added better admin validation in various places [prevent crashes]
- Updated some documentation
- Fixed Besluiten API spec defects
- Fixed rendering the admin detail pages for read-only resources
- Fixed the cache for resultaattypeomschrijvinggeneriek
- Updated to latest Django security release
- Improved help-text for read-only fields
- Fixed CI
🎉 First release of Open Zaak.
Features:
- Zaken API implementation
- Documenten API implementation
- Catalogi API implementation
- Besluiten API implementation
- Autorisaties API implementation
- Support for external APIs
- Admin interface to manage Catalogi
- Admin interface to manage Applicaties and Autorisaties
- Admin interface to view data created via the APIs
- NLX ready (can be used with NLX)
- Documentation on https://open-zaak.readthedocs.io/
- Deployable on Kubernetes, single server and as VMware appliance
- Automated test suite
- Automated deployment