Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 22.1
edited by Erik Bakker
on 2022/11/10 12:27
Change comment: There is no comment for this version
To version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +244 - Forgotten Frontiers
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 +In the last sprint, we released several stability options, mainly regarding the deletion behavior within the platform. We also released an update to the flow configuration of Mendix systems to avoid conflicts with another module that you could be using in Mendix, the Excel Importer.
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>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
4 4  
5 -===== Runtime Release Notes =====
5 +====New Features====
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 +* General - Support: System admins can manually log out other users with active sessions. This is added to cover certain edge cases regarding locked flows. (#1197)
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 +====Major Changes====
15 15  
16 -=====Minor changes=====
11 +* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
12 +** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
13 +** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
14 +** Users can un-transfer the Exit/Entry connector in the Create phase either by selecting one of the integrations or both of the integrations of the Exit/Entry connector. This process is also successful when the Exit/Entry connector is in the Deploy phase.
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.
21 -
22 -
23 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. (#783)
27 -* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
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)
17 +
18 +* Design - API Data Model: Users can remove entities that were once part of a gateway message of an API operation that has been removed/un-transferred from the Create Phase. (#1577)
19 +* Create - Flow Designer: Create phase - The help text of the “Max fetch size” property of the “IMAP idle channel adapter” better reflects its behavior and usage. (#1410)
20 +* eMagiz Connector - Flow Configuration: The issue where the new eMagizConnector Mendix module would cause conflicts with the Mendix Excel Importer module has now been resolved.
21 +** If you already have a synchronous messaging flow for a Mendix connector system, this flow must be reset before creating a new release. Make sure this new version is included in your next release. Failing to do so can break error handling for these synchronous entry flows.
22 +** After setting the new release as active, the Mendix application has to be stopped and started to use the new image. This doesn’t have to be done right away, you can await the following restart.