Changes for page 230 - Petite Peaks
Last modified by Carlijn Kokkeler on 2024/09/27 09:36
From version 312.1
edited by Erik Bakker
on 2024/09/09 09:54
on 2024/09/09 09:54
Change comment:
There is no comment for this version
To version 308.1
edited by Carlijn Kokkeler
on 2024/08/26 15:58
on 2024/08/26 15: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 -22 9-Xpath Alignment1 +228 - Monitoring Mania - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,10 +1,19 @@ 1 -During our recent sprint cycle, we made several improvements tokeepourmodel runningsmoothly.Wealso madesomesmallchangesto variousXPath-relatedpartsof theportal. Please find all our changesandbug fixes 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.22 9-XPath Alignment||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]]. 4 4 5 5 ====Minor changes==== 6 -* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers," "receive a notification mail," or "both." On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you *still* need to enable triggers manually if you have manually disabled them before deploying. This can be done via the Manage phase. 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) 7 7 8 8 ====Bug fixes==== 9 -* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component (#727) 10 -* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if it exists. (#1010) 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)