Skip to Content
Last modified by Erik Bakker on 2025/02/13 07:36
From version 188.1
edited by Carlijn Kokkeler
on 2024/01/15 14:58
Change comment: There is no comment for this version
To version 190.1
edited by Carlijn Kokkeler
on 2024/01/17 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -In the last sprint cycle, we focused on ....
1 +In the last sprint cycle, we focused on providing new cloud templates that improve auto-healibng. Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done.
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
... ... @@ -8,12 +8,9 @@
8 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 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 10  
11 -=====Minor changes=====
12 -
13 -
14 14  ====Bug fixes====
15 15  
16 -* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
13 +* Design - Message Mapping: We have improved our merging functionality within our Store offering to avoid unexpected results after merging.
17 17  * Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
18 18  
19 19