Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 208.1
edited by Carlijn Kokkeler
on 2024/03/25 12:18
Change comment: There is no comment for this version
To version 189.1
edited by Carlijn Kokkeler
on 2024/01/15 16:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +212 - Failover Fiesta
Content
... ... @@ -1,18 +1,16 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
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.217 - Template Tango||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 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the cloud template release notes for more information.
7 7  
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"]].
8 8  
9 -=====Minor changes=====
11 +====Bug fixes====
10 10  
11 -* Manage - Monitoring: The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. (#951)
12 -* Deploy - Releases: Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. (#1137)
13 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
13 13  
14 -====Bug fixes====
15 15  
16 -* Generic - Login: In the login screen, users can now press "enter" to log in when the username field is selected.
17 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
18 -* Create - Flow Designer: An issue has been fixed where removing an onramp linked to a combined entry was impossible. (#1021)