Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 695.1
edited by Erik Bakker
on 2024/08/26 16:11
on 2024/08/26 16:11
Change comment:
There is no comment for this version
To version 705.1
edited by Erik Bakker
on 2024/09/09 10:16
on 2024/09/09 10:16
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 8-MonitoringMania1 +229 - Xpath Alignment - Content
-
... ... @@ -3,89 +3,52 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release wehavedonemanyimprovements tothemonitoringgraphsinManage.Moreover,wehavemade someimprovements tothe missingproperties andunusedproperties overviewsand didseveralbug fixes. Find out all improvements&bug fixes below!6 +**Hi there, eMagiz developers!** In this release, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Find out all the improvements and bug fixes below! 7 7 8 -== **Feedback Items** == 9 -//__Grafana improvements__// 10 -* The following graphs now show the unit of measurement per time frame (i.e. bytes/2h) 11 -** Queue Statistics - Overview 12 -*** Message Througput 13 -** Event Streaming Statistics - Overview 14 -*** Bytes In 15 -*** Bytes Out 16 -*** Messages In 8 +== **Deployment Plan Improvements** == 17 17 18 - [[image:Main.Images.ReleaseBlog.WebHome@release-228-eventsteamingstats.png]]10 +//__Monitoring Trigger - Improvements__// 19 19 20 -* The following graph now shows an improved unit of measurement 21 -** Runtime Statistics - Key Metrics 22 -*** Log events are counted as a sum instead of a maximum per data point. 23 -* The following data measurement graphs indicate whether the component was on or off when hovering over the data points. 24 -** Runtime Statistics - Other Metrics 25 -*** Data measurements 26 -** Queue Statistics - Other Metrics 27 -*** Data measurements 12 +* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option. 28 28 14 +[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]] 29 29 30 -* The Memory and CPU usage table inthe Runtimestatisticsdisplaysthe maximum value inagiventimeperiodthatisselected.31 -* Pressingthe 'show main dashboard' button returnsbackto theunfiltered masterdashboard.32 -* For detailedviewsthe 'show main dashboard' buttonis on theleft.33 -* Graphs ona pageshare the same crosshair.34 -* The stylingon HTTP statistics when there are no (un)successful requests within a timeframe has been improved.35 -* Forselectiondropdowns theselectedvariablesarecked to the topfor easydeselection.16 +* The "Disable" option under this step type comes with two new options. 17 +** End Action. Here, you can opt for the following three options 18 +*** Auto-enable triggers 19 +*** Send email 20 +*** Both 21 +* Duration. Here, you can define a waiting period that states how long eMagiz should wait before executing the end action. The value of this field needs to lie between 15 and 120 minutes. Note that the timer starts when your deployment plan's "disable" step is finished. 36 36 37 -[[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]] 38 -[[image:Main.Images.Release Blog.WebHome@release-228-maindashboard.png]] 23 +[[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]] 39 39 40 -//__Failover deployment plan__// 41 -The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan. 25 +{{warning}}Note that the end action is only triggered when the deployment plan cannot complete all steps. When all steps are completed, the timer is **stopped**. Therefore, we advise adding the "enable" step back to the end of your deployment plan to ensure that triggers are automatically re-enabled when the deployment is successfully finished. This also covers cases where the deployment plan is automatically executed (by pressing the play button), after which the user moves on to other things and forgets to move away from the page once the deployment plan is completed. 26 + 27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}} 42 42 43 -//__Edit mode flow testing__// 44 -Test messages can now be edited or removed while in the edit mode of the flow testing functionality. 45 45 46 -//__Missing properties overview__// 47 -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. 48 -[[image:Main.Images.Release Blog.WebHome@release-228-missing-properties.png]] 30 +//__Default Plan - Improvements__// 49 49 50 -//__Legacy release notes__// 51 -The legacy release notes tab has been removed. 32 +* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment). 52 52 53 - //__SSLhelptext__//54 -The SSLsectioninruntime settingshasmoreelaboratehelptext.34 +* The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed. 35 +* The "Enable" step is added as the last step of your deployment plan. 55 55 56 -[[image:Main.Images.Release Blog.WebHome@release-228-ssl-enabled.png]] 57 - 58 -//__Memory warning__// 59 -A pop-up with a warning will be shown when containers are configured with less memory than recommended. 37 +[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]] 60 60 61 -[[image:Main.Images.Release Blog.WebHome@release-228-memory-settings.png]] 62 - 63 -//__Reuse test messages__// 64 -It is now possible to reuse the test messages created in other flows within the routing and vice versa. 65 - 66 -//__Unused properties__// 67 -We added logging for when properties are deleted from the unused properties screen. 68 - 69 -[[image:Main.Images.Release Blog.WebHome@release-228-unused-properties.png]] 70 - 71 71 == **Bug Fixes** == 72 -//__ Legacyproperties__//73 -We removedlegacyproperties in connections throughtheeMagizMendixconnector.Thismeans thatyouwillnotgetblockedanymore whendeploying toProduction.40 +//__XPath Header Enricher - Help Text Improvement__// 41 +We have added various help text segments that explain which results the XPath expression will yield in this context and how to ensure that a list of results is returned when executing this action. 74 74 75 -//__ Exceedingmemory__//76 -We fixed a bug wherenewmachines could bedeployedwith exceedingmemory.43 +//__XPath Configuration - Transformation__// 44 +We fixed a bug that caused data loss once you switched between the "custom xpath" and "if exists" options when adding a filter or transformation in the Create Transformation tooling. 77 77 78 -//__Copy paste__// 79 -The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. 80 - 81 81 == **Fancy Forum Answers** == 82 82 83 83 As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: 84 84 85 -* [[Character array is missing "e" notation exponential mark>>https://my.emagiz.com/p/question/172825635703914491||target="blank"]] 86 -* [[Error when creating XSD>>https://my.emagiz.com/p/question/172825635703914508||target="blank"]] 87 -* [[Warning log - "Invalid cookie header">>https://my.emagiz.com/p/question/172825635703927026||target="blank"]] 88 -* [[Param_path variable remains empty when including question mark>>https://my.emagiz.com/p/question/172825635703939749||target="blank"]] 50 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]] 51 +* [[How to process messages with invalid XML content like "">>https://my.emagiz.com/p/question/172825635703939917||target="blank"]] 89 89 90 90 == **Key Takeaways** == 91 91