Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 322.1
edited by Erik Bakker
on 2026/03/22 21:39
Change comment: There is no comment for this version
To version 100.1
edited by Erik Bakker
on 2023/08/01 15:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -264 - Strict Separation
1 +202 - New Equilibrium
Content
... ... @@ -1,31 +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 cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
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.202 - New Equilibrium.WebHome||target= "blank"]].
4 4  
5 -==== Minor changes ====
5 +=====New features=====
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)
7 +* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 +* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 +* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
16 16  
17 -==== Bug fixes ====
12 +=====Minor changes=====
18 18  
19 -* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
20 -* 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)
21 -** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
22 -** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
23 -** 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)
24 -* 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.
25 -* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
26 -* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
14 +* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 +* Deploy - Releases: The infographic has been updated.
16 +* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 +* Deploy - Property release: Names of properties can be created/removed/edited.
18 +* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 +* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966)
20 +* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 +* Infrastructure: Tightened security policies for a more secure infrastructure.
27 27  
28 -==== Remarks ====
23 +====Bug fixes====
29 29  
30 -* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
31 -* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)
25 +* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 +* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 +* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 +* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 +* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 +* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 +* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 +* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 +* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 +* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 +* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
36 +