Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 198.1
edited by Erik Bakker
on 2024/02/13 15:07
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
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,16 @@
1 -In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.214 - System Symphony||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
8 -* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
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 -
12 -* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
13 -* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
14 -
15 15  ====Bug fixes====
16 16  
17 -* Create - Flow Designer: The help text of the Group attribute has been improved.
18 -* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 -* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
13 +* Design - Message Mapping: We have improved our merging functionality within our Store offering to avoid unexpected results after merging.
14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
20 20  
21 21