Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 243.1
edited by Erik Bakker
on 2025/04/08 16:42
Change comment: There is no comment for this version
To version 356.1
edited by Erik Bakker
on 2026/09/20 21:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -242 - Stability Score
1 +277 - First Farewell
Content
... ... @@ -1,20 +1,26 @@
1 -In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our most significant change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better control their resource management within the cloud models. In addition, we released various improvements in the platform regarding clarity and stability.
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>>Main.Release Information.Release Blogs.242 - Stability Score.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 -* Cloud - Templates: We have implemented a feature for cloud models to improve resource management control within your production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
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 -====Minor Changes====
9 +==== Minor Changes ====
10 10  
11 -* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer.
12 -* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
13 -* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector.
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.
14 14  
15 -====Bug fixes====
16 +===== Bug Fixes ====
16 16  
17 -* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307)
18 -* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19 -* Manage - Triggers: You can no longer add HTML in the trigger fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
20 -
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)