Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 309.1
edited by Erik Bakker
on 2026/02/10 09:01
Change comment: There is no comment for this version
To version 358.1
edited by Erik Bakker
on 2026/09/20 22:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +277 - First Farewell
Content
... ... @@ -1,16 +1,26 @@
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 includes many smaller improvements across the platform's various phases. It also introduces a **new** runtime image in response to several CVE reports. Furthermore, it marks the **end of support** for our Event Streaming-related alerting for models still running on our old infrastructure (Aiven).
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.277 - First Farewell.WebHome||target="blank"]].
4 4  
5 -==== New Features ====
5 +==== Major 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 - API MAM Migration: Topic alerting for the legacy Aiven-based Kafka topics has been marked as **End of Support**. This means the functionality will keep running as-is, but we will no longer provide support, bug fixes, or updates for this feature. This only affects customers who have not yet migrated to our new event streaming broker.
10 10  
11 -==== Remarks ====
9 +==== Minor Changes ====
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.
11 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V360.WebHome||target="blank"]] for **all** customers is available.
12 +* General - UI/UX: Some UI elements have been replaced with newer versions, which should improve User experience.
13 +* Design - System Message: OpenAPI import functionality from the system message of an API integration is revised and improved. The functionality lets you select the desired path and operation to import from the selected OpenAPI file. Also, it imports both the request and response messages for the selected operation and sets them as root. (#1421)
14 +* Design - CDM: We improved the loading of data model-related information. This improves performance when interacting with larger data models.
15 +
16 +===== Bug Fixes ====
17 +
18 +* Design - Solution Design: Event Streaming processors with errors in their message mapping are also displayed when the Design phase “Only errors” switch is enabled. (#1422)
19 +* Design - Solution Design: Sorting of the tenants on a multi-tenant system is aligned between Capture and Design. (#1736)
20 +* Design - System message: Fixed two typos found when attempting to delete and edit annotations. (#1813)
21 +* Design - Event Streaming: The prompt for entering edit mode correctly references event streaming when the integration type is event streaming. (#1780)
22 +* Create - Flow designer: We fixed an issue regarding the HTTP security support object that prevented the underlying flow from working even though the security was disabled.
23 +* Create - Properties tab: Improved the logic for property highlighting when selecting a component for properties with similar names. (#1774)
24 +* Deploy - Releases: We fixed a minor typo when a step is determined not to be relevant in the deployment plan. (#1781)
25 +* Deploy - Missing flows for runtimes: The pop-up also includes the display name of the system in Design. (#1812)
26 +* Manage - Flows With Error Messages: Filter option on the "flow with error messages" page to be carried over to the pop-up when opening the overview of a specific flow containing errors (#1766)