Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 671.1
edited by Carlijn Kokkeler
on 2024/08/14 09:17
Change comment: There is no comment for this version
To version 683.1
edited by Carlijn Kokkeler
on 2024/08/26 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +228 - Monitoring Mania
Content
... ... @@ -3,52 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release we have many fixes! Mainly for flow testing, the deploy phase, and alerting for hybrid models several small bugs have been resolved. Apart from these fixes, search functionality has been added to the start/stop flows screen. Moreover, the tracing information for errorChannel messages in flow test traces has been improved and we have enabled our new queue trigger functionality for redelivery-enabled messaging queues. Find out all about it below!
6 +**Hi there, eMagiz developers!** This release
7 7  
8 8  == **Feedback Items** ==
9 -//__Tracing information__//
10 -Tracing errors in flow testing has been improved.- For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V312.WebHome||target="blank"]] is available.
9 +//__Grafana improvements__//
10 +* The throughput now shows the unit of measurement in the Queue statistics.
11 +* The units of measurement have been improved in the following graphs:
12 +** Runtime detail: Log events are counted as a sum instead of a maximum per data point. Data measurements show if a runtime is on or off.
13 +** Queue detail: Data measurements show if a queue is on or off.
14 +** Event streaming: The Bytes in and out are not a rate per seconds but dynamic based on the time frame selected. The messages in are counted not based on per second but also dynamic based on the time frame selected.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
16 +[[image:Main.Images.Release Blog.WebHome@release-228-eventsteamingstats.png]]
13 13  
14 -//__Start/stop flows search__//
15 -It is now possible to search in the Start/Stop flows overview.
18 +* The Memory and CPU usage table in the Runtime statistics displays the maximum value in a given time period that is selected.
19 +* Pressing the 'show main dashboard' button returns back to the unfiltered master dashboard.
20 +* For detailed views the 'show main dashboard' button is on the left.
21 +* Graphs on a page share the same crosshair.
22 +* The styling on HTTP statistics when there are no (un)successful requests within a timeframe has been improved.
23 +* For selection dropdowns the selected variables are locked to the top for easy deselection.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-searchterm.png]]
25 +[[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]]
26 +[[image:Main.Images.Release Blog.WebHome@release-228-maindashboard.png]]
18 18  
19 -//__Message redelivery queue triggers__//
20 -The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
21 -
22 -== **Bug Fixes** ==
23 -//__Update namespace resources__//
24 -The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
28 +//__Failover deployment plan__//
29 +The deployment plan steps with type 'Failover' is now deprecated, meaning they can no longer be added to a deployment plan.
25 25  
26 -//__Queue triggers hybrid models__//
27 -We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to use the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
31 +//__Edit mode flow testing__//
32 +Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
28 28  
29 -//__Internal/External recipients__//
30 -You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly. Cases where this was applied incorrectly have been automatically fixed.
34 +//__Missing properties overview__//
35 +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.
36 +[[image:Main.Images.Release Blog.WebHome@release-228-missing-properties.png]]
31 31  
32 -//__Tenant queue trigger__//
33 -We have fixed a case where a tenant queue trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
38 +//__Legacy release notes__//
39 +The legacy release notes tab has been removed.
34 34  
35 -//__Area selector__//
36 -We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
41 +//__SSL helptext__//
42 +The SSL section in runtime settings has more elaborate helptext.
37 37  
38 -//__Runtime overview__//
39 -The runtime overview will now always display the correct container version.
44 +[[image:Main.Images.Release Blog.WebHome@release-228-ssl-enabled.png]]
45 +
46 +//__SSL helptext__//
47 +A pop-up with a warning will be shown when containers are configured with less memory than recommended.
40 40  
41 -//__List of flows__//
42 -We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of runtimes that will be restarted.
49 +[[image:Main.Images.Release Blog.WebHome@release-228-memory-settings.png]]
43 43  
44 -//__Deploy prevention__//
45 -We have resolved a bug that prevented you from deploying anything on a newly created model.
51 +== **Bug Fixes** ==
52 +//__Legacy properties__//
53 +We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production.
46 46  
47 -//__Cancel button__//
48 -The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
49 49  
50 -//__Log test execution__//
51 -If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
52 52  
53 53  == **Fancy Forum Answers** ==
54 54