Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 20.1
edited by Erik Bakker
on 2022/11/08 08:49
Change comment: There is no comment for this version
To version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +241 - Wild West
Content
... ... @@ -1,29 +1,31 @@
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 have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
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.241 - Wild West.WebHome||target="blank"]].
4 4  
5 -===== Runtime Release Notes =====
5 +====Minor 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 +* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 +* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608)
9 +* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually.
10 +* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 +* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 +* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
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.
15 -
16 -=====Minor changes=====
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.
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)
15 +
16 +* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17 +* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18 +* Design - Message Definition: small improvements are introduced:
19 +** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20 +** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21 +* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597)
22 +* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
23 +* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24 +* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
25 +* Create - Components: The browser page now displays the correct page title (#1509)
26 +* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27 +* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
28 +* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526)
29 +* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408)
31 +* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)