Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 325.1
edited by Carlijn Kokkeler
on 2024/09/25 16:56
Change comment: There is no comment for this version
To version 307.1
edited by Carlijn Kokkeler
on 2024/08/26 15:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +228 - Monitoring Mania
Content
... ... @@ -1,13 +1,19 @@
1 -During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
1 +During our recent sprint cycle, we have done several improvements to the monitoring graphs in Manage. Moreover, we have done several improvements in deploy architecture and flow testing. Please find out all our changes & bug fixes below.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]].
4 4  
5 -====New features====
6 -* All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more on our documentation page (LINK).
7 -
8 8  ====Minor changes====
9 -* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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. (#1277)
9 +* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended. (#1423)
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 - History: We added logging for when properties are deleted from the unused properties screen. (#1428)
12 +* 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. (#1436)
13 +* 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)
10 10  
11 11  ====Bug fixes====
12 -* Manage - Explore: Queues with illegal characters will not generate errors anymore. As a result they can be explored and if needed removed from your model.
13 -* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
16 +* 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)
17 +* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392)
18 +* Create - Flow Testing: It is now possible to reuse the test messages created in other flows within the routing and vice versa. (#1274)
19 +* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)