Changes for page 241.1 - Wild West
Last modified by Erik Bakker on 2025/04/04 08:35
From version 220.1
edited by Erik Bakker
on 2025/01/27 13:22
on 2025/01/27 13:22
Change comment:
There is no comment for this version
To version 188.1
edited by Carlijn Kokkeler
on 2024/01/15 14:58
on 2024/01/15 14:58
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 37- FabulousFlow1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,23 +1,19 @@ 1 -In the last sprint ,we focused on improving the flow back and forth between the various phases in eMagiz bysolving several feedback items related to Design,Create, and Design and the interaction betweenthese three phases. We have alsoimproved the memorycalculation for all runtimesrunning on a Windows machine. Moreover, we have updatedthe stylingof our graphs inthe Manage phase.1 +In the last sprint cycle, we focused on .... 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 37- FabulousFlow||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. 4 4 5 -==== MinorChanges====5 +=====New features===== 6 6 7 -* Create - Flow Designer: Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter. (#1461) 8 -* Create - Flow Designer: Styling of the following components has been updated. (#1544) 9 -** XML to EDI transformer 10 -** EDI to XML transformer 11 -** XML to UN/EDIFACT transformer 12 -** UN/EDIFACT to XML transformer 13 -* Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine. 14 -* Manage - Statistics: We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards. 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"]]. 15 15 11 +=====Minor changes===== 12 + 13 + 16 16 ====Bug fixes==== 17 17 18 -* 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) 19 -* Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559) 20 -* Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532) 21 -* Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523) 22 -* Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511) 23 -Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out. 16 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models. 17 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements. 18 + 19 +