Changes for page 277 - First Farewell
Last modified by Erik Bakker on 2026/09/23 16:09
From version 359.1
edited by Erik Bakker
on 2026/09/23 16:09
on 2026/09/23 16:09
Change comment:
There is no comment for this version
To version 227.1
edited by Erik Bakker
on 2025/02/10 09:31
on 2025/02/10 09:31
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 77-FirstFarewell1 +238 - Preparation Paraside - Content
-
... ... @@ -1,27 +1,12 @@ 1 - Thisreleaseincludesmanysmaller improvementsacrosstheplatform'svariousphases.Italsointroducesa**new**runtimeimagein response toseveralCVEreports.Furthermore,itmarks the**endofsupport**for ourEventStreaming-related alertingformodelsstillrunningon our oldinfrastructure(Aiven).1 +In the last sprint, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.277-FirstFarewell.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.238 - Preparation Paradise.WebHome||target="blank"]]. 4 4 5 -==== Major Changes====5 +====Minor Changes==== 6 6 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. 7 +* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system. 8 +* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]]. 8 8 9 -==== Minor Changes====10 +====Bug fixes==== 10 10 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 -* 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) 12 +* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)