Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 239.1
edited by Erik Bakker
on 2025/04/04 08:35
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 -2411 - Wild West
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,10 +1,19 @@
1 -In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use.
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.212 - Failover Fiesta||target="blank"]].
4 +
5 +=====New features=====
6 +
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"]].
10 +
11 +=====Minor changes=====
12 +
13 +
3 3  ====Bug fixes====
4 4  
5 -* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release.
6 -* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release.
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.
7 7  
8 -====Remarks====
9 9  
10 -* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.