Skip to Content

Changes for page 261 - Taking Charge

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +255 - Fine Form
Content
... ... @@ -1,16 +1,23 @@
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 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine.
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.255 - Fine Form.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 - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers and our flow testing will be made available.
8 +* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400)
9 +* Capture - Settings - Integrations: Update column label to be more consistent (#1710)
10 +* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163)
11 +* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711)
12 +* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708)
10 10  
11 -==== Remarks ====
14 +==== Bug fixes ====
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.
16 +* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320)
17 +* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534)
18 +* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571)
19 +* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668)
20 +* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059)
21 +* Deploy - eMagiz Connector: Resolved the issue where, in some edge cases, downloading the latest release when staring the eMagiz Connector could lead to an error, preventing the connector from starting.
22 +
23 +