Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 229.1
edited by Erik Bakker
on 2025/02/25 08:29
Change comment: There is no comment for this version
To version 188.1
edited by Carlijn Kokkeler
on 2024/01/15 14:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -239 - Modern Talking
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,19 @@
1 -In the last sprint, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us we are ready to launch the new eMagiz Mendix Connector to our community. With this release we will make available for all new Mendix systems in models running on the current-generation architecture. Subsequently we will implement a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -====New Features====
5 +=====New features=====
6 6  
7 -* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. The new connector is better integrated in your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
8 -** A migration wizard will be released later which allows you to easily and smoothly migrate your current legacy Mendix connectors to the new Mendix connector.
7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 9  
10 -====Minor Changes====
11 +=====Minor changes=====
11 11  
12 -* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in view mode of the Flow Designer. (#870)
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Create - Flow Creation: Payload root Qname support object for the API gateway infra is not containing duplicates now. (#1517)
17 -* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the [id].[system].[flow] convention, or when that value is longer than expected. (#1566)
16 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
17 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
18 +
19 +