Skip to Content

Changes for page 276 - API, API

Last modified by Erik Bakker on 2026/09/10 08:00
From version 313.1
edited by Erik Bakker
on 2026/02/12 09:08
Change comment: There is no comment for this version
To version 353.1
edited by Erik Bakker
on 2026/09/10 07:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +276 - API, API
Content
... ... @@ -1,43 +1,16 @@
1 -This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that update a multitude of configurations on cloud and on-premises machines. Furthermore, we have a series of smaller improvements to enhance your everyday work.
1 +This release includes several smaller improvements across the platform's phases. We also updated certain parts of our Mendix project to their latest versions.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.276 - API, API.WebHome||target="blank"]].
4 4  
5 -==== New Features ====
5 +==== Minor Changes ====
6 6  
7 -* API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply:
8 -** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
9 -** Clients that obtain an access token with an authorization code will also obtain a //refresh token//, which can be used to obtain a subsequent access token without user intervention. This refresh token is valid for **24 hours**, meaning the client application must call the eMagiz API gateway at least that often; otherwise, manual intervention is needed to authorize the call again.
7 +* General - Platform: Replaced several older widgets with newer equivalents. As a result the look and feel of various parts of the platform are changed.
10 10  
11 -==== Major changes ====
9 +===== Bug Fixes ====
12 12  
13 -* Deploy -> Architecture (Upgrade): The authorization server has been incorporated into the environment template. The first deployment will happen in Deploy > Architecture. All infra-side updates will be covered within the environment upgrade.
14 -* Deploy -> Architecture (Upgrade): Double lane models can now upgrade to an intermediate environment template first, before upgrading to the final template in case of a service-impacting template. This allows us to verify that all containers in the backup zone are running properly before the final, service-affecting template is applied.
11 +* Deploy - Release: We improved the activating release logic that will prevent some uncertainty issues during the deployment of the release in Deploy phase.
12 +* 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)
15 15  
16 -==== Minor changes ====
17 -
18 -* Generic -> Authorization Server: Improved security headers of the endpoints of eMagiz-hosted authorization servers.
19 -* Design -> Security: Removed the security setting button from the API Gateway catalog. You can still access the settings from the design overview.
20 -* Deploy: All pop-ups showing important information, like a key, secret, or password, are structured so that the data is visualised and can be copied by the user when the “show data” action button is utilised. (#1735)
21 -* Deploy -> User Management: Any reference to a URL related to the authorization server is now shown, including ‘https://'.
22 -* Deploy -> Architecture: Endpoint URL for routes is available on the view/edit pop-up of specific routes on the Deploy architecture. Additionally, the construction of how it is provided as a help text, and this feature is only available for the AWS model. (#792)
23 -* Manage -> Monitoring (HTTP Statistics): The details page will now show the display name of the user that initiated a request instead of the Id. Note: For this change to be applied to your environment, you need to adhere to the following requirements:
24 -** The MAM API-Gateway migration must be completed
25 -** You must be running on the latest environment template
26 -*** Single lane: R18
27 -*** Double lane: R20
28 -*** The gateway container must be deployed with the latest eMagiz runtime (version 3.5.0 or up)
29 -
30 -==== Bug fixes ====
31 -
32 -* Generic: System display names in all phases are updated progressively with the change in the Capture phase. All other places where the system display name was allowed to be changed are now disallowed, and changes can only be made from Capture. (#449)
33 -* Design - System Message: After successfully importing an OpenAPI file in the system request/response message, the user remains on the same page. (#1308)
34 -* Design - System (Failover): When you identify a system as a failover and subsequently create the integration on that system, you do not need to push multiple versions anymore before you can deploy your release.
35 -* Design - Architecture: We inform the user via the History overview when an overwrite action is triggered in the test environment for their model upon request. (#1697)
36 -* Create - Flow Designer: The help text of the XPath expression field on the XPath splitter is updated. (#1467)
37 -* Create - Transformation: Users can mark all XPath expressions as checked by a button in the transformation page. This button will remove only the warnings that come with the import from store feature, and will delete only those with an XPath expression.
38 -* Create - Add Integrations: When creating a new event processor with JSON as input and XML as output, this configuration is reflected in the generated flow in Create after transfer. Now the message format is automatically recognized and handled correctly, similar to API Gateway operations. (#1752)
39 -* Deploy - Architecture (Start/Stop Flows): Your search phrase when searching for “component names” in this overview can now contain special characters present in the technical name of your inbound component(s). (#1639)
40 -
41 41  ==== Remarks ====
42 42  
43 -* Generic: When retrieving information from our infrastructure about available customer agents, we improved performance by reducing the amount of data we retrieve and process.
16 +* Updated our __emagiz.com__ certificate.