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 185.1
edited by CarlijnKokkeler
on 2024/01/15 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 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,32 +1,27 @@
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 ....
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>>Main.Release Information.Release Blogs.212 - Failover Fiesta||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)
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 +* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
17 17  
18 -==== Bug fixes ====
10 +=====Minor changes=====
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)
12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
28 28  
29 -==== Remarks ====
19 +====Bug fixes====
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)
21 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 +
27 +