Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 290.1
edited by Erik Bakker
on 2025/11/04 12:44
Change comment: There is no comment for this version
To version 306.1
edited by Erik Bakker
on 2026/02/10 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -256 - Power Up
1 +261 - Taking Charge
Content
... ... @@ -1,15 +1,16 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>>> Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
1 +This release includes a lot of updates to our platform. We are releasing some beta features for customers utilizing our latest version of the API Gateway allowing to use multiple authentication methods. On top of that we will release a new environment template that will update a multitude of configurations on cloud and on-premise machines. Furthermore, we have a series of smaller improvements to bring delight to your everyday work.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.256 - Power Up.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
4 4  
5 -==== Bug fixes ====
5 +==== New Features ====
6 6  
7 -* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8 -* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9 -** From store functionality for API Gateway is restored.
10 -** Additionally, users can import store item to synchronous system message - response message.
11 -* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12 -* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13 -* Deploy - Containers: Debug icon has on hover text (#1725)
14 -* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
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 authorization code will also obtain a ~~refresh token~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for *24 hours*, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again.
15 15  
11 +==== Remarks ====
12 +
13 +* The advised Docker version for on-premises deployments has been updated from 24.0.7 to 29.1.3. Documentation on how to update Docker can be found at:
14 +** [[Linux>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
15 +** [[Windows>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]]
16 +* An infrastructure change has been applied to the container registry to improve how traffic is managed within our own environment.