Skip to Content

Changes for page 276 - API, API

Last modified by Erik Bakker on 2026/09/10 08:00
From version 355.1
edited by Erik Bakker
on 2026/09/10 08:00
Change comment: There is no comment for this version
To version 326.1
edited by Erik Bakker
on 2026/04/09 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -276 - API, API
1 +265 - Maintenance Mode
Content
... ... @@ -1,20 +1,8 @@
1 -This release includes various smaller improvements throughout the various phases of the platform. On top of that, it introduces a structured and simple way to navigate to our API MAM functionality for all models using the API Pattern in combination with the API Key security option.
1 +This release includes various mandatory infrastructural updates. Due to our quality standards and our upcoming migration of our platform to a newer version of our underlying Mendix technology, we decided to bundle all user-facing functionality into the upcoming release, which we have been developing. As a result, we have little to share with you on this one.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.276 - API, API.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.265 - Maintenance Mode.WebHome||target="blank"]].
4 4  
5 -==== New Features ====
6 -
7 -* General - API MAM Migration: Migration wizard for API MAM for API Key API gateway models. This migration wizard enables you to transform your API gateway environment to support multiple authentication methods (OAuth, API key, and basic auth).
8 -
9 -==== Minor Changes ====
10 -
11 -* General - Platform: Replaced several older widgets with newer equivalents. As a result, the look and feel of various parts of the platform have changed.
12 -
13 -===== Bug Fixes ====
14 -
15 -* Flow Designer - Save and Create New Version: We fixed a bug that prevented users from transferring their flows to Deploy when their initial action was to create an “Autosaved version” of the flow. (#1816)
16 -* Deploy - Release: We improved the release activation logic to prevent some uncertainty issues during the deployment of the release in the Deploy phase.
17 -
18 18  ==== Remarks ====
19 19  
20 -* Updated our //__emagiz.com__// certificate.
7 +* General - Infrastructure: An update will be applied to our internal infrastructure to improve the version management of authorization server databases.
8 +* General - Infrastructure: An update will be applied to our internal infrastructure to adhere to the latest standards and versions of underlying code bases.