Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 190.1
edited by Carlijn Kokkeler
on 2024/01/17 08:56
Change comment: There is no comment for this version
To version 218.1
edited by Erik Bakker
on 2025/01/13 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +236 - Another Agent
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,16 +1,20 @@
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.
1 +In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.236 - Another Agent||target="blank"]].
4 4  
5 -=====New features=====
5 +====Major Changes====
6 6  
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"]].
10 10  
11 -====Bug fixes====
9 +====Minor Changes====
12 12  
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.
11 +* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options.
12 +* Deploy - Overview: Spring6 pop-up has been removed.
13 +* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet.
15 15  
15 +====Bug fixes====
16 16  
17 +* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
18 +* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543)
19 +* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
20 +