Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
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 263.1
edited by Erik Bakker
on 2025/06/17 09:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +247 - Help Out
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,16 +1,12 @@
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 +This release focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
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.247 - Help Out.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Bug fixes ====
6 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 -====Bug fixes====
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.
15 -
16 -
7 +* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 +* Create - Flow designer: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 +* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 +* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow is corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 +* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 +* Manage - Explore (Queue Browser): The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)