Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 297.1
edited by Erik Bakker
on 2025/12/01 09:18
Change comment: There is no comment for this version
To version 359.1
edited by Erik Bakker
on 2026/09/23 16:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -258 - Vale Bene
1 +277 - First Farewell
Content
... ... @@ -1,17 +1,27 @@
1 -This release features various updates to our platform, just before the holiday season. This will be our last release of the year. We will be back releasing more on **January 15th**. With this release, you can enjoy an improved user experience in specific sections of the platform.
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.258 - Vale Bene.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 -==== Minor changes ====
5 +==== Major Changes ====
6 6  
7 -* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary.
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.
8 8  
9 -==== Bug fixes ====
9 +==== Minor Changes ====
10 10  
11 -* Design - Data Model (Message Format): Viewing and editing permissions for the message format of different message types are fixed. The checks are corrected for all message types. (#1050)
12 -* Create - Add Integrations: Assigning a target namespace to messages based on the system being identified as a "SOAP entry connector" is corrected. Event processors no longer get the target namespace. (#1183)
13 -* Create - System Message / Data Model Message: The UI is updated immediately after removing restrictions for an attribute without the need to refresh the page. (#1707)
14 -* Create - Add Resource (Multiple places): Fixed a bug where when uploading a new (flow) resource in Create, one could select the eMagiz-generated “message definition” & “message transformation”. These, along with two deprecated resource file types, have been removed from the selectable types.
15 -* Create - Help Texts: We have fixed a bug in our help texts where the text would not show for specific input fields.
16 -* Manage - Queue dashboard: Updated message throughput panel to sometimes filter out spikey first and last observations (#1589)
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.
17 17  
16 +===== Bug Fixes ====
17 +
18 +* Capture - Requirements Designer: Fixed default message format changing inappropriately. As a result, we will not change the default message format when the user previously selected a non default option (#1805)
19 +* 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)
20 +* Design - Solution Design: Sorting of the tenants on a multi-tenant system is aligned between Capture and Design. (#1736)
21 +* Design - System message: Fixed two typos found when attempting to delete and edit annotations. (#1813)
22 +* Design - Event Streaming: The prompt for entering edit mode correctly references event streaming when the integration type is event streaming. (#1780)
23 +* 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.
24 +* Create - Properties tab: Improved the logic for property highlighting when selecting a component for properties with similar names. (#1774)
25 +* Deploy - Releases: We fixed a minor typo when a step is determined not to be relevant in the deployment plan. (#1781)
26 +* Deploy - Missing flows for runtimes: The pop-up also includes the display name of the system in Design. (#1812)
27 +* 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)