Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 304.1
edited by Carlijn Kokkeler
on 2024/08/26 14:29
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 -228 - Monitoring Mania
1 +212 - Failover Fiesta
Content
... ... @@ -1,18 +1,16 @@
1 -During our recent sprint cycle, w...
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.228 - Monitoring Mania||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Community - Release Notes: The legacy release notes tab has been removed.
7 -* Create - Flow Testing: Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
8 -* Deploy - Architecture: The SSL section in runtime settings has more elaborate helptext.
9 -* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended.
10 -* Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.
11 -* Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview.
12 -* Manage - Monitoring: We have done many improvements to the Monitoring graphs. Find out all improvements in our [[release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]]. (#866)
5 +=====New features=====
13 13  
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 +
14 14  ====Bug fixes====
15 -* Create - Flow Designer: We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. (#1065)
16 -* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392)
17 -* Create - Flow Testing: It is now possible to reuse the test messages from the onramp in the routing and vice versa in flow testing. (#1274)
18 -* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)
12 +
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.
15 +
16 +