Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 15.1
edited by Erik Bakker
on 2022/10/28 16:23
Change comment: There is no comment for this version
To version 323.1
edited by Erik Bakker
on 2026/03/22 21:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -186 - Daemon Switch
1 +264 - Strict Separation
Content
... ... @@ -1,35 +1,32 @@
1 -The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a slew of smaller feedback items and bug fixes.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
5 +==== Minor changes ====
7 7  
8 -=====Minor changes=====
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.
9 9  
10 -* Create - Flow designer: You can now see who/when a resource was changed on a resource view page.
11 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
12 -* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
13 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
14 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
15 -* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type.
16 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
17 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
18 -* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
19 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
20 -* Deploy - Properties: You can use enter key to search on the property overview page.
21 -* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component.
22 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
23 -* Administration - Licenses: Added event streaming storage usage of your models.
24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
18 +==== Bug fixes ====
26 26  
27 -====Bug fixes====
28 -* Deploy - Properties: Improved the layout of the cron trigger generator page
29 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
30 -* Create - Flow designer: While editing an exit flow, the system message is not editable.
31 -* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
32 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
33 -* Create - Flow designer: Comparing two flow versions works again.
34 -* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
35 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
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)
28 +
29 +==== Remarks ====
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)