Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 21.1
edited by Erik Bakker
on 2022/11/08 09:01
Change comment: There is no comment for this version
To version 282.1
edited by Erik Bakker
on 2025/09/21 21:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +253 - Rince Repeat
Content
... ... @@ -1,29 +1,22 @@
1 -The release brings the next step of the Design store to the public and releases a new version of the eMagiz Mendix Connector that unlocks those using it to migrate to the next generation runtime. On top of that, we have several feedback items and bug fixes.
1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
4 4  
5 -===== Runtime Release Notes =====
5 +==== Major Changes ====
6 6  
7 -The 6.0.0 release of the eMagiz Mendix connector (EMC) is here. This eMagiz Mendix connector (EMC) version is compatible with the 3rd generation runtime. On top of that, it includes updates on most of the userlib libraries to have the latest security fixes in place. For specific information, please check out this link to the [[release notes>>Main.Release Information.Runtime.eMagiz Mendix Connector - 600.WebHome||target="blank"]].
7 +* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976)
8 8  
9 -=====New features=====
10 -* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
11 -** The Design Store can also be opened from the Mapping and Data Model screens.
12 -** The Design Store now offers search options for store items, including Transformations and Data Models.
13 -** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model.
14 -** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model.
9 +==== Minor changes ====
15 15  
16 -=====Minor changes=====
17 17  
18 -* Create - Flow Designer: Improved the help texts of the Kafka components to explain specific performance and load-balancing considerations better and added detailed information on how messages (including headers) are converted to/from Kafka records.
19 -* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
20 -* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have.
12 +* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message.
13 +** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]
14 +* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment.
21 21  
16 +==== Bug fixes ====
22 22  
23 -====Bug fixes====
24 -* Design - Store: Importing store items from response messages doesn't cause issues anymore.
25 -* Design - Store: Importing response messages and transformation to API integration is possible.
26 -* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document.
27 -* Create - Flow Designer: Fix bugs when copying and pasting components in the G3 configuration.
28 -* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
29 -* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)
18 +* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702)
19 +* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703)
20 +* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706)
21 +* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)
22 +** When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push.