Per-service Changelog
API Gateway
1.6.1 (2023-06-23)
1.6.0 (2023-06-16)
Release Notes
🎁 Features
Add the possibility to redirect requests from one service to another
It is now possible to redirect all traffic from one service to another service or another version of the service by setting environment variables.
1.5.0 (2023-06-06)
Release Notes
⚒️ Improvements
Added DNS Caching
DNS Caching was added in the gateway to speed up requests and improve the stability of the API Gateway.
Authentication Service
2.2.0 (2024-06-13)
Release Notes
🎁 Features
Logout the user on password reset completion or user deletion
When a user completes a password reset or a user is deleted, the tokens belonging to the user are removed.
The tokens which are removed include all tokens related to oAuth1, oAuth2, MFA and SSO.
⚒️ Improvements
Dependencies updated
2.1.0 (2023-04-12)
Release Notes
🎁 Features
OpenID Connect is added as a authentication method
Users can now authenticate with OpenID Connect identity providers that support the
client_secret_basicauthentication method.
⚒️ Improvements
Validation from the application logo is removed
Users can now add anything they want as the application logo.
This used to be only hashes that were used by the image service.
2.0.5 (2022-09-19)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
🐞 Bugs Fixed
Applications with an invalid type can not be created anymore
Configurations Service
2.0.4 (2022-09-16)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
2.0.3 (2022-06-28)
Release Notes
⚒️ Improvements
Internal improvements that make the service less dependent on changes in other services.
Data Service
1.4.0 (2025-01-21)
Release Notes
🎁 Features
The Schema access control options are now more granular
Schema
createMode,readMode,updateModeanddeleteModehave been improved to be more consistent and accept multiple granular options.For further information please refer to the data access management documentation.
Executing a Transition by name
When executing a Transition, instead of having to find and provide the
id, you can now choose to provide thenameof a Transition. This improvement will make code clearer and easier to re-use across your different clusters.
New Transition permissions The following permissions have been added to allow the execution of Transitions:
Execute any Transition in any Schema:
TRANSITION_DOCUMENTSExecute any Transition in a specific Schema:
TRANSITION_DOCUMENTS:{SCHEMA_NAME}Execute a specific Transition for a specific Schema:
TRANSITION_DOCUMENTS:{SCHEMA_NAME}:{TRANSITION_NAME}
Group permissions
Staff members can now be assigned permission to perform operations on a Document that is linked to their Groups. The permissions
VIEW_DOCUMENTS,UPDATE_DOCUMENTS,DELETE_DOCUMENTSandTRANSITION_DOCUMENTSare now supported. (Including their sub-permissions e.g.VIEW_DOCUMENTS:{SCHEMA_NAME})
Task Action quality of life improvements
The Task Action now supports the
priorityfieldThe Task Action is now supported for Transition
afterActions.
🚨 Deprecation Warnings
Legacy schema access control options
Most of the existing createMode, readMode, updateMode and deleteMode values have been deprecated in favor of the revamped access control options.
1.3.1 (2024-07-12)
Release Notes
🎁 Bugs Fixed
Deleted users no longer cause issues when being linked or unlinked from a document
General stability issues with background processes resolved
1.3.0 (2023-10-27)
Release Notes
🎁 Features
Added a skipCount() RQL function that instructs the listing function not to execute and return the total count.
🐞 Bugs Fixed
Known
SERVICE_EXCEPTIONs thrown on RQL errors are now resolved toINVALID_RQL_EXCEPTIONsThe
<and>characters may now be used in RQL when double encoded.
1.2.1 (2023-08-29)
Release Notes
⚒️ Improvements
Improved error thrown when multiple text indexes are created
🐞 Bugs Fixed
Input conditions on date-time fields now working correctly
Allowed removing broken indexes
If creating an index fails, the index is not added to the schema anymore
1.2.0 (2022-11-16)
Release Notes
🎁 Features
RQL support for update array item end point
It is now possible to filter array items by RQL when doing an update or deletion.
⚒️ Improvements
Documentation improvements
🐞 Bugs Fixed
Unique index is not created on array items to avoid long database lock up
1.1.1 (2022-09-15)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
1.1.0 (2022-02-16)
Release Notes
🎁 Features
Allow targeting schema’s by name in the url
All the end points that were previously called with a schema id can now also be called by schema name.
Specific schema permissions
It is now possible to have permissions specifically for a schema. e.g. VIEW_DOCUMENTS:notes gives you permission to view all the documents on the schema with the name notes.
⚒️ Improvements
Swagger documentation is improved
Comments end points are marked as deprecated. Small mistakes in other end points are fixed.
🐞 Bugs Fixed
While adding a property to a schema the configuration field was not marked as required
Dispatchers Service
1.1.0 (2023-09-20)
Release Notes
🎁 Features
Added a
PUTendpoint for updating DispatchersAdded name, description and tags fields to Dispatchers
Name is unique against all Dispatchers
Added name and description fields to Actions
Name is unique against Actions within a Dispatcher
⚒️ Improvements
Updated validation for Dispatchers and Actions
1.0.5 (2022-09-15)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Events Service
1.2.0 (2024-06-13)
Release Notes
🎁 Features
Event subscriptions can be marked as retriable
When services subscribe to events, they now can indicate the subscription is retriable.
When sending an event to a retriable subscription fails, it will be retried up to 3 times.
1.1.0 (2023-11-17)
Release Notes
🎁 Features
Added a
skip_count()RQL operator. Would instruct the listing functions not to execute/return the total count.
🐞 Bugs Fixed
RQL
Using the
containsoperator inside anoroperator now works as expectedThe
neoperator now behaves as expectedKnown
SERVICE_EXCEPTIONs thrown on RQL errors are now resolved toINVALID_RQL_EXCEPTIONsSorting on id now behaves as expected
Querying on
content.<name>_idnow works as expected
1.0.7 (2022-09-23)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Files Service
1.1.0 (2023-08-09)
Release Notes
🎁 Features
Added File Service settings
A new settings property
disableForceDownloadForMimeTypesmay be configured to override the File Service’s default behavior of enforcing file downloads and enable viewing of files directly in the browser for selected mime types.
⚒️ Improvements
Improved the error message for creating a file without a request body
🐞 Bugs Fixed
An empty string is now a valid value in an array of tags
Fixed an RQL issue that would not consider the use of the limit operator
1.0.3 (2023-04-19)
1.0.2 (2022-09-13)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Groups Service
1.1.6 (2022-09-16)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
1.1.5 (2022-04-15)
Release Notes
🎁 Features
Publish events for each group update
When a group has been updated, a tag has been added/removed, or when a custom field is added/removed the group_updated-event is sent out.
⚒️ Improvements
Documentation - Correct the request body of the remove custom fields endpoint
Updated openapi.yaml file so the example makes sense
🐞 Bugs Fixed
Cannot query on a custom field with a name ending with _id
Localizations Service
1.1.8 (2022-09-20)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
1.1.7 (2022-06-28)
Release Notes
⚒️ Improvements
Expand the accepted language codes to at least include all entries in ISO 639-1.
🐞 Bugs Fixed
Users with some languages could not use the service correctly.
When non-existent localization code is translated, fall back to the default language.
🚨 Deprecation Warnings
GET /languagesis now deprecated
Logs Service
1.0.1 (2023-04-19)
1.0.0 (2022-11-18)
Release Notes
🎁 Features
View the API access logs
View and query the API access logs from the comfort of your ExH cluster.
Mail Service
1.2.1 (2024-06-04)
Release Notes
⚒️ Improvements
Emails can be blocked from actually being sent
Behind the scenes we can block emails being sent to certain domains/email addresses when needed. Only to be used on request if you want to protect your email sending reputation.
1.2.0 (2022-10-12)
Release Notes
⚒️ Improvements
Increased the stability of the service Service discovery is now based on DNS and more reliable.
Internationalized email address support Email addresses using non ascii characters, such as
二ノ宮@黒川.日本, are now supported via updating our validation to be based on RFC 6530.
🐞 Bugs Fixed
Inconsistencies in querying on certain fields (
template_id,updateTimestamp, …) with RQL have been resolved.
Notifications Service
1.1.2 (2024-04-16)
Release Notes
⚒️ Improvements
Firebase internal server errors are retried
When Firebase Cloud Messaging returns an internal server error while sending a push notification, we now retry to up to 2 times
1.1.1 (2024-02-16)
Release Notes
⚒️ Improvements
Unusable Firebase tokens are removed automatically
Tokens reported by Firebase as valid but not (or no longer) usable, are automatically removed.
Invalid formatted tokens are ignored as proper detection is currently not feasible.
1.1.0 (2024-02-01)
Release Notes
🎁 Features
Added support for Firebase HTTP V1 notifications
Starting from the 20th of June the old Legacy HTTP Protocol for notifications will stop working.
The total count in the listing endpoints can now be disabled
Added a
skip_count()RQL operator. Would instruct the listing endpoints not to execute/return the total count to increase performance.
⚒️ Improvements
Improved Swagger documentation
Swagger documentation was heavily extended
🐞 Bugs Fixed
RQL
Using the
containsoperator inside anoroperator now works as expectedThe
neoperator now behaves as expectedKnown
SERVICE_EXCEPTIONs thrown on RQL errors are now resolved toINVALID_RQL_EXCEPTIONs
Updating the settings without a body now throws a correct
EMPTY_BODY_ERRORThe Link Notification Type name now correctly shows
linkinstead ofmessage
1.0.9 (2022-09-21)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Payments Service
1.3.2 (2022-09-15)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
1.3.1 (2022-08-03)
Release Notes
🐞 Bugs Fixed
AppStore: Transactions with a changed
transaction_idvalue do no longer cause issues.An active subscription being detached from a user will now correctly update the
expireTimestampof the relevant entitlement.
🚨 Deprecation Warnings
The
lastTransactionIdfield in the App Store subscriptions is replaced bylastWebOrderId. App Store subscriptions are returned by theGET /appStore/subscriptions endpoint.
1.3.0 (2022-07-14)
Release Notes
🎁 Features
Complete a purchase for another user
When the payment details of a Play Store or App Store purchase are known, it is now possible to complete the purchase process for another user. This allows users with administrative privileges to move a subscription from one user to another or help users with (technical) difficulties.
Re-evaluate the state of a Play Store or App Store subscription
We now allow to trigger a re-evaluation of the subscription state. If the Play Store or App Store subscription state is out of sync, a re-evaluation will bring the state back in sync with the information reported by the payment provider.
Detach a Play Store or App Store subscription from a user
It is now possible to remove a Play Store and App Store subscription. This allows the subscription to be moved to another user.
⚒️ Improvements
Improved the integration with Play Store and App Store
The Play Store integration got a big overhaul and the stability of the App Store integration has been improved.
Automatically detach subscriptions on user removal
When a user account is deleted, the subscriptions linked to the account are removed. This allows users that deleted their account to reclaim their subscription when creating a new account.
🐞 Bugs Fixed
Play Store subscriptions no longer end up in the
expired_from_billingstatus after a successful renewalApp Store receipts with awkward ordering are now handled correctly
Invalid RQL queries are now reported with the correct error
Prescriptions Service
1.1.19 (2023-01-19)
1.1.18 (2022-09-22)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
1.1.17 (2022-04-29)
Release Notes
🐞 Bugs Fixed
Sometimes the 7/30 days past timestamp was not updated
The PeriodExpiryCheckStartJob scheduler stopped after a while
Users with some languages could not use the service correctly
Profiles Service
1.2.0 (2024-01-02)
Release Notes
🎁 Features
Added a
skip_count()RQL operator. Would instruct the listing endpoints not to execute/return the total count to increase performance.
🐞 Bugs Fixed
RQL
Using the
containsoperator inside anoroperator now works as expectedThe
neoperator now behaves as expectedKnown
SERVICE_EXCEPTIONs thrown on RQL errors are now resolved toINVALID_RQL_EXCEPTIONs
Removing fields
patient_idcan now be removed from profile groupsAn empty list of fields to remove is now correctly handled
Attempts to remove an id or timestamp field are now correctly handled
1.1.4 (2022-09-21)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Reports Service
1.0.13 (2022-09-22)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Tasks Service
1.6.0 (2024-01-02)
Release Notes
🎁 Features
Added a
skipCount()RQL operator. Would instruct the listing functions not to execute/return the total count.
🐞 Bugs Fixed
RQL
Known
SERVICE_EXCEPTIONs thrown for RQL errors are now resolved toINVALID_RQL_EXCEPTIONsDouble encoding the
<and>characters when searching for them now works.
1.5.0 (2023-07-12)
Release Notes
🎁 Features
Added API Requests
API Requests are a summary of the requests made to API Functions. They can be helpful to monitor and debug API Function calls.
Add functionality to consult logs of API Requests
API Functions may now include logging statements during execution. These logs are saved as API Request Logs.
⚒️ Improvements
Increased performance of API Functions and Direct Function Execution
Improve the error message for tasks of which the output could not be determined
Updated the function runtimes
The new runtimes are documented in the public documentation.
🐞 Bugs Fixed
The last task log line sometimes did not show up
Trying to add Node12 as a runtime resulted in an error
Retrieving the task logs for a non-existing task resulted in a SERVER_EXCEPTION
Retrieving the logs for a new function right after the first run could result in a SERVER_EXCEPTION
Returning a number from an API function as body resulted in a SERVER_EXCEPTION
1.4.0 (2023-05-31)
Release Notes
🎁 Features
Functions can be used as an HTTP(s) endpoint
API Functions can be used to create your own endpoints.
Send a task failed event
When a task fails, a
task_failedevent is triggered.
⚒️ Improvements
Allow empty body in the execute endpoint.
The execute-endpoint can now be called with an empty body whereas previously, an empty objects had to be provided.
🐞 Bugs Fixed
Task logs with a timestamp equal to the end marker are now shown
RQL is now correctly marked as required in the OpenAPI documentation
1.3.2 (2023-04-19)
1.3.1 (2022-09-13)
Release Notes
⚒️ Improvements
Increased the stability of the service
Service discovery is now based on DNS and more reliable.
1.3.0 (2022-08-09)
Release Notes
🎁 Features
Function retry policy
Users can now enable a retry policy on a function, which retries tasks of the function that fail. The user can choose between retrying all errors or specifying specific errors that should be retried.
Task-specific logs
It is now possible to list the logs of a specific task. This allows users to easily find what happened during a task run.
🚨 Deprecation Warnings
GET /functions/:functionName/logsis now deprecated
1.2.0 (2022-03-30)
Release Notes
🎁 Features
Execute a function synchronously for its response
Via the following request: POST /functions/:name/execute a function can now be executed directly, and the caller gets the output of the function execution.
Execute functions based on a schedule
You can now schedule the execution of a function on a fixed interval.
Fetch the details of a function
The details of a function are returned via GET /functions/:name
Ability to disable/enable a function
Via the following request: GET /functions/:name/enable & GET /functions/:name/disable Will affect the ability for a function to be executed or not
⚒️ Improvements
A single task service instance can now run multiple tasks in parallel
After creating a function all details are returned
The tasks now keep track of their initiator
🐞 Bugs Fixed
Function code can now be updated together with other configuration
Unknown fields are no longer causing errors while updating a function
Errors for invalid function names are now correctly reported
Template Service
1.0.15 (2022-09-23)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
Users Service
1.5.0 (2024-06-13)
Release Notes
🎁 Features
An event is triggered when a password reset is completed
The
password_reset_completedevent is triggered when a user completes a password reset.
Clean up on user deletion
When a user is deleted the password reset and account activation requests belonging to that user are removed as well.
1.4.0 (2024-03-13)
Release Notes
🎁 Features
Pin code mode for the account activation and forgot password flows
The pin code mode is an alternative mode for the account activation and forgot password flows.
The mode is targeted to use cases where the end user might need to manually input the secret in your application.
List and remove the account activation and forgot password requests
New endpoints to list and remove the account activation and forgot password requests.
Helps to provide insight and control over these flows.
(Rate)limit account activation and password reset requests
The amount, rate and lifetime of account activation and password reset requests that are requested for an account are now controlled.
View and update verification settings
Control the behavior of the account activation and password reset flows.
⚒️ Improvements
Fallback to the maximum RQL limit if larger is requested
Supplying an RQL limit higher than the maximum now set it to the maximum rather than the default limit
🐞 Bugs Fixed
Empty strings are now included in the response correctly rather than hidden
Corrected the OpenAPI documentation of the
PUT /passwordresponse
🚨 Deprecation Warnings
The newly introduced verification settings
limit_hash_activation_requestsandlimit_hash_forgot_password_requestsare marked as deprecated immediately.They’re only provided to help existing applications transition to make use of the new (rate)limiting feature.
1.3.0 (2023-11-03)
Release Notes
🎁 Features
Added a
skip_count()RQL operator. Would instruct the listing functions not to execute/return the total count.
🐞 Bugs Fixed
Staff enlistment roles can now be queried correctly with the RQL
containsoperatorDeleted users referenced in an Activation or New Password Request now cause a
USER_UNKNOWN_EXCEPTIONto be thrownEmpty strings are no longer accepted for permissions
RQL
Using the
containsoperator inside anoroperator now works as expectedThe
neoperator now behaves as expectedKnown
SERVICE_EXCEPTIONs thrown on RQL errors are now resolved toINVALID_RQL_EXCEPTIONs
1.2.0 (2023-04-12)
Release Notes
🎁 Features
OpenID Connect is added as a authentication method.
The end points that return users now also provide
oidc_linkswith theprovider_idand thesubject_idfields.Other endpoints for users with a password are blocked for OpenID Connect users.
1.1.12 (2022-11-18)
Release Notes
⚒️ Improvements
Requests can now take up to 10 seconds
Queries for GET requests are no longer restricted by the 3 seconds timeout. The timeout is now configurable on our side and is set to 10 seconds by default.(previously also implemented in 1.1.11)
🐞 Bugs Fixed
Trying to add a non existing role to a user no longer affects the user
(Regression) The RQL select operation no longer affects updates
1.1.11 (2022-11-15)
1.1.10 (2022-09-22)
Release Notes
⚒️ Improvements
Increased the stability of the service:
Service discovery is now based on DNS and more reliable.
🐞 Bugs Fixed
Expiry field set incorrectly in patient enlistments
1.1.9 (2022-03-10)
Release Notes
🎁 Features
Configurable Email Template ID's
The activation, reactivation and password reset mail template can now be configured by the end user.
1.1.8 (2021-12-22)
Last updated