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 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -264 - Strict Separation
1 +191 - Fifty Fifty
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 +The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.WebHome||target="blank"]].
4 4  
5 -==== Minor changes ====
5 +=====New features=====
6 +* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7 +** Error Message is to evaluate the headers of the original message which resulted in an error.
8 +** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9 +** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
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)
13 +=====Major changes=====
16 16  
17 -==== Bug fixes ====
15 +* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
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)
17 +=====Minor changes=====
27 27  
28 -==== Remarks ====
19 +* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20 +* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21 +* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24 +* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25 +* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26 +* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27 +* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
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)
29 +====Bug fixes====
30 +* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31 +* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32 +* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33 +* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34 +* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35 +* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
36 +