Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 136.1
edited by CarlijnKokkeler
on 2023/10/23 16:40
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 -207 - Aligned State
1 +264 - Strict Separation
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,46 +1,32 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>Main.Release Information.Runtime Images.V2.0.0||target="blank"]] [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
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 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
14 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
23 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
18 +==== Bug fixes ====
27 27  
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 28  
29 +==== Remarks ====
29 29  
30 -====Bug fixes====
31 -
32 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
33 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
35 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
38 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
41 -
42 -
43 -
44 -=====Infra and image changes=====
45 -
46 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
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)