Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 325.1
edited by Erik Bakker
on 2026/03/22 21:45
Change comment: There is no comment for this version
To version 319.1
edited by Erik Bakker
on 2026/02/23 08:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -264 - Strict Separation
1 +262 - Good News
Content
... ... @@ -1,32 +1,28 @@
1 -This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform.
1 +This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers. Furthermore, we have a series of smaller improvements to enhance your everyday work.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.262 - Good News.WebHome||target="blank"]].
4 4  
5 5  ==== Minor changes ====
6 6  
7 -* Deploy - User management: Several new functionalities are released, improving the user experience when dealing with user management. To experience these improvements, you need to be running on the latest version of our API Gateway and/or Event Streaming offering.
8 -** When you click “Apply to environment” in Deploy > User management, a pop-up now displays all pending changes. You can select only the changes you want to apply (cherry-pick), and any related dependencies will be automatically selected. This helps prevent mistakes and ensures consistency when applying updates. With this enhancement, you can more easily and safely customize configurations per environment.
9 -** For fully migrated models (using DSH for Eventstreaming), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
10 -** For fully migrated models (using API MAM for API gateway), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
11 -* Deploy - Property: When saving a property, we now perform an optimization check. These improvements help reduce redundancy and keep property configurations cleaner and easier to maintain.
12 -** If other properties share the same name and value, we will recommend grouping them to improve manageability.
13 -** If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list.
14 -** If none of the linked runtimes use the property, we recommend removing it.
15 -* Deploy - Releases: It is no longer possible to try to deploy a release that contains runtimes that are not linked to any flows in the architecture. (#1066)
16 -* Deploy - Architecture: Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
7 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 +* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553)
9 +* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794)
10 +* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341)
11 +* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users.
12 +* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537)
13 +* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537)
14 +* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily.
15 +* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz.
16 +** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger.
17 17  
18 18  ==== Bug fixes ====
19 19  
20 -* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
21 -* Design - Swagger Configuration: Errors related to the generation of the Swagger UI in eMagiz have been resolved. Users will no longer encounter errors when generating JSON (new cases). (#1424) (#1337)
22 -** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
23 -** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
24 -** Schema validation has been extended to help prevent configuration mistakes. Existing errors related to referencing or schema definitions in the request/response body may still be present. However, when opening the edit page and clicking Save, the extended validation will be triggered. If the configuration results in an error, the validation will indicate this so it can be corrected before saving. (#924)
25 -* Create - Flow Testing: Users will get a pop-up error message related to their broken test case and will be asked to fix it. For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer.
26 -* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
27 -* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
20 +* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
21 +* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
22 +* Create - Flow Designer: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
23 +* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
24 +* Manage - Explore: Error message is much more descriptive when the container is not running (#1321)
28 28  
29 29  ==== Remarks ====
30 30  
31 -* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
32 -* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)
28 +* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.