Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 310.1
edited by Erik Bakker
on 2026/02/10 09:01
Change comment: There is no comment for this version
To version 28.1
edited by Erik Bakker
on 2022/11/24 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +188 - Close Encounters
Content
... ... @@ -1,16 +1,21 @@
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.
1 +The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
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>>Main.Release Information.Release Blogs.188 - Close Encounters.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 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.
7 +* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8 +* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 +* Deploy - Deployment plan: When a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11 +** After five times, the runtime will remain in the stopped state.
10 10  
11 -==== Remarks ====
13 +====Bug fixes====
14 +* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
15 +* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
17 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
18 +* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
12 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.
20 +====Remarks====
21 +* Mendix Runtime has been upgraded to Mendix 9.19.0.