Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 323.1
edited by Erik Bakker
on 2026/03/22 21:41
Change comment: There is no comment for this version
To version 237.1
edited by Erik Bakker
on 2025/03/24 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -264 - Strict Separation
1 +241 - Wild West
Content
... ... @@ -1,32 +1,36 @@
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 +In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
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 +* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 +* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
9 +* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
10 +* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 +* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 +* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
13 +* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
17 17  
18 -==== Bug fixes ====
15 +====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)
17 +* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
18 +* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
19 +* Design - Message Definition: Two minor improvements are introduced:
20 +** The widget prevents users from adding the same message attribute within a message definition multiple times.
21 +** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
22 +* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
23 +* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
24 +* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
25 +* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
26 +* Create - Components: The browser page now displays the correct page title (#1509)
27 +* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
28 +* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
29 +* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
30 +* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
31 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
32 +* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
28 28  
29 -==== Remarks ====
34 +====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)
36 +* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.