Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 301.1
edited by Erik Bakker
on 2026/01/15 09:25
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 -259 - Improve Infinitely
1 +261 - Taking Charge
Content
... ... @@ -1,21 +1,16 @@
1 -This release features various updates to our platform, just after the holiday season. Apart from various more minor improvements, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V350.WebHome||target="blank"]] for **all** customers.
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.259 - Improve Infinitely.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 -==== New features ====
5 +==== New Features ====
6 6  
7 -* General - Runtime Image: Maintenance update where we primarily updated Spring Boot from version 3.4.1 to 3.5.8 and ensured all our external libraries are up-to-date.
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.
8 8  
9 -==== Minor changes ====
11 +==== Remarks ====
10 10  
11 -* Create - Flow Designer: Selector expression is added on the channel interceptors page. (#1738)
12 -* Manage - Error Messages: Search by complete flow name functionality is added to the flows with error messages page. Additionally, the grid is updated to improve the page's appearance. (#1738)
13 -
14 -==== Bug fixes ====
15 -
16 -* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739)
17 -* Create - Flow Designer: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891)
18 -* Create - Flow Designer: The same display name was being used for two similar support objects, which caused confusion. The incorrectly labeled object has now been renamed. The second "Byte array length header (de)serializer" has been renamed to "ByteArrayRawSerializer". (#1751)
19 -* Deploy - Known Hosts String: When you create a new property and select the drop-down called “Data type”, choose the option called “Known hosting string”. Behind the “Value” field, a cog wheel appears. It leads you to a pop-up. In this pop-up, the Host and Port fields have been swapped. We did it because this ordering aligns with the common defaults used across IT systems. (#1749)
20 -* Monitoring - Runtimes: two graphs, namely “Problematic runtimes memory usage” and “Max memory usage”, are fixed and show correct information. (#1654)
21 -
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.