v.1.13.1

Cleanup

• Update documentation (old paths).
• Cleaning up code (Generic naming of method, streamlining parameters).

v.1.13.0

Architecture

• Introducing Onion Layer Architecture to OMC.

  Chance the root of the solution from EventsHandler to OMC.

  

• Make SecretsManager use OmcConfiguration class instead of internal pass.

• Update documentation by introducing Architecture Schema to chapter 2.

Refactor

• Improve versioning of OMC (support major, minor, path components of the version).
• Improve AspNetExceptionsHandlerAttribute class.
• Add substitutes for health check endpoints for ZHV/Open Services.

  ZHV/Open Services doesn't contain dedicated health check endpoints.

• Create dedicated test controllers for various test endpoints, OMC, Notify, ZHV.

NotifyNL OMC v1.12.4

Features:

• Introduce "loading context" fallback strategy to override appsettings.json using environment variables
• New test endpoint: Test/OMC/TestConfigs to check if all required configurations are in place
• Cleanup with config file

NotifyNL OMC v1.12.3

Fix

• The definition of Docker image in Dockerfile was still using .NET 7 for ASP.NET and SDK

UI

• Change formatting of dates passed to Notify or Open Services as strings to: dd-MM-yyyy

NotifyNL OMC v1.12.2

Maintenance

• Upgrade all projects within the solution to .NET 8 framework
• Upgrade all packages to their latest versions compatible with .NET 8 (Notify UK will not be updated)

This should solve vulnerability issues (memory leak, with System.Text.Json library), detected before)

• Cleanup of the solution according to the new .NET 8 clean code standards

NotifyNL OMC v1.12.1

Maintenance:

• Do not treat deserialization issues as error codes any more. Use API response wrapper, to return them as 206, so Notificatie API Web service, would not retry sending them anymore
• Standardize and cleanup API responses from OMC to include error code, details, and notification JSON in almost all cases

NotifyNL OMC v1.12.0

Maintenance

• Update environment variables to be more readable and follow DDD nomenclature.

What was changed:

Old (OMC v1.11.3 and below)	New (OMC v1.12.0 and above)		Comments
.NET settings
ASPNETCORE_ENVIRONMENT	ASPNETCORE_ENVIRONMENT	Nothing was changed
OMC settings
OMC_AUTHORIZATION_JWT_SECRET	OMC_AUTH_JWT_SECRET	Longer AUTHORIZATION was renamed to shorter AUTH
OMC_AUTHORIZATION_JWT_ISSUER	OMC_AUTH_JWT_ISSUER
OMC_AUTHORIZATION_JWT_AUDIENCE	OMC_AUTH_JWT_AUDIENCE
OMC_AUTHORIZATION_JWT_EXPIRESINMIN	OMC_AUTH_JWT_EXPIRESINMIN
OMC_AUTHORIZATION_JWT_USERID	OMC_AUTH_JWT_USERID
OMC_AUTHORIZATION_JWT_USERNAME	OMC_AUTH_JWT_USERNAME
OMC_FEATURES_WORKFLOW_VERSION	OMC_FEATURE_WORKFLOW_VERSION	Singular instead of plural
ZGW (Open Services) settings
USER_AUTHORIZATION_JWT_SECRET	ZGW_AUTH_JWT_SECRET	In OMC Workflow v1: JWT token is shared between OpenZaak, OpenKlant v1, and Besluiten API components (that's how it was designed by third-party Maykin Media, and communicated a couple of times that they decided not to change this model of authorization)	"USER" nomenclature was proposed long time ago on the early stage of OMC development - drawing the line between "ours" (OMC) and "theirs" ("Open Services" from Maykin Media). After the OMC project matured, business-oriented approach was introduced instead. What was called "Open Services" turns out to be "ZGW" (case-oriented workflow)
USER_AUTHORIZATION_JWT_ISSUER	ZGW_AUTH_JWT_ISSUER
USER_AUTHORIZATION_JWT_AUDIENCE	ZGW_AUTH_JWT_AUDIENCE
USER_AUTHORIZATION_JWT_EXPIRESINMIN	ZGW_AUTH_JWT_EXPIRESINMIN
USER_AUTHORIZATION_JWT_USERID	ZGW_AUTH_JWT_USERID
USER_AUTHORIZATION_JWT_USERNAME	ZGW_AUTH_JWT_USERNAME
USER_API_KEY_OPENKLANT	ZGW_AUTH_KEY_OPENKLANT	In OMC Workflow v2: OpenKlant v2 is using API key instead of JWT token, but OpenZaak and Besluiten API components are still sharing the same JWT token	API Keys were grouped under the same AUTH node as JWT tokens (which seems to be very logical)
USER_API_KEY_OBJECTEN	ZGW_AUTH_KEY_OBJECTEN
USER_API_KEY_OBJECTTYPEN	ZGW_AUTH_KEY_OBJECTTYPEN
USER_DOMAIN_OPENNOTIFICATIES	ZGW_ENDPOINT_OPENNOTIFICATIES	Since OMC is now allowing to accept a combination of domain + path + endpoint version, this environment variable was renamed to "endpoint"
USER_DOMAIN_OPENZAAK	ZGW_ENDPOINT_OPENZAAK
USER_DOMAIN_OPENKLANT	ZGW_ENDPOINT_OPENKLANT
USER_DOMAIN_BESLUITEN	ZGW_ENDPOINT_BESLUITEN
USER_DOMAIN_OBJECTEN	ZGW_ENDPOINT_OBJECTEN
USER_DOMAIN_OBJECTTYPEN	ZGW_ENDPOINT_OBJECTTYPEN
USER_DOMAIN_CONTACTMOMENTEN	ZGW_ENDPOINT_CONTACTMOMENTEN
USER_WHITELIST_ZAAKCREATE_IDS	ZGW_WHITELIST_ZAAKCREATE_IDS
USER_WHITELIST_ZAAKUPDATE_IDS	ZGW_WHITELIST_ZAAKUPDATE_IDS
USER_WHITELIST_ZAAKCLOSE_IDS	ZGW_WHITELIST_ZAAKCLOSE_IDS
USER_WHITELIST_TASKASSIGNED_IDS	ZGW_WHITELIST_TASKASSIGNED_IDS
USER_WHITELIST_DECISIONMADE_IDS	ZGW_WHITELIST_DECISIONMADE_IDS
USER_WHITELIST_MESSAGE_ALLOWED	ZGW_WHITELIST_MESSAGE_ALLOWED
USER_WHITELIST_TASKOBJECTTYPE_UUID	ZGW_VARIABLE_OBJECTTYPE_TASKOBJECTTYPE_UUID	Some environment variables holding "whitelist" values could have been misleading. More business-oriented naming was used instead + singular instead of plural
USER_WHITELIST_MESSAGEOBJECTTYPE_UUID	ZGW_VARIABLE_OBJECTTYPE_MESSAGEOBJECTTYPE_UUID
USER_VARIABLES_OBJECTEN_MESSAGEOBJECTTYPE_VERSION	ZGW_VARIABLE_OBJECTTYPE_MESSAGEOBJECTTYPE_VERSION
USER_WHITELIST_DECISIONINFOOBJECTTYPE_UUIDS	ZGW_VARIABLE_OBJECTTYPE_DECISIONINFOOBJECTTYPE_UUIDS
Notify settings
OMC_API_BASEURL_NOTIFYNL	NOTIFY_API_BASEURL	Notify client settings (base URL + API key)
USER_API_KEY_NOTIFYNL	NOTIFY_API_KEY
USER_TEMPLATEIDS_DECISIONMADE	NOTIFY_TEMPLATEID_DECISIONMADE	Templates are related to how Notify is working and expecting so, all environment variables were grouped under the same category as Notify client settings
USER_TEMPLATEIDS_EMAIL_ZAAKCREATE	NOTIFY_TEMPLATEID_EMAIL_ZAAKCREATE
USER_TEMPLATEIDS_EMAIL_ZAAKUPDATE	NOTIFY_TEMPLATEID_EMAIL_ZAAKUPDATE
USER_TEMPLATEIDS_EMAIL_ZAAKCLOSE	NOTIFY_TEMPLATEID_EMAIL_ZAAKCLOSE
USER_TEMPLATEIDS_EMAIL_TASKASSIGNED	NOTIFY_TEMPLATEID_EMAIL_TASKASSIGNED
USER_TEMPLATEIDS_EMAIL_MESSAGERECEIVED	NOTIFY_TEMPLATEID_EMAIL_MESSAGERECEIVED
USER_TEMPLATEIDS_SMS_ZAAKCREATE	NOTIFY_TEMPLATEID_SMS_ZAAKCREATE
USER_TEMPLATEIDS_SMS_ZAAKUPDATE	NOTIFY_TEMPLATEID_SMS_ZAAKUPDATE
USER_TEMPLATEIDS_SMS_ZAAKCLOSE	NOTIFY_TEMPLATEID_SMS_ZAAKCLOSE
USER_TEMPLATEIDS_SMS_TASKASSIGNED	NOTIFY_TEMPLATEID_SMS_TASKASSIGNED
USER_TEMPLATEIDS_SMS_MESSAGERECEIVED	NOTIFY_TEMPLATEID_SMS_MESSAGERECEIVED
Notify settings
SENTRY_DSN	SENTRY_DSN	Nothing was changed
SENTRY_ENVIRONMENT	SENTRY_ENVIRONMENT

NotifyNL OMC v1.11.3

Maintenance:

• Cleanup after the hackathon regarding the changes supporting organizations
• Documentation update that OMC workflow v2 is supporting citizens and organizations

Features:

• Improve UX of logging serialization errors

v.1.11.2: Merge pull request #86 from Worth-NL/task_company_v2

Enables notifications for tasks with cases that have a non-natural person as an involvedparty defined through the betrokkeneUri field.

NotifyNL OMC v1.11.1

This patch fixes an issue that prevents the OMC from parsing roles in OpenZaak if they are of the type niet_naturlijk_persoon.