Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23

From version 309.1
edited by Carlijn Kokkeler
on 2024/08/26 16:09
Change comment: There is no comment for this version
To version 296.1
edited by Carlijn Kokkeler
on 2024/08/12 13:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -228 - Monitoring Mania
1 +227 - Fix Frenzy
Content
... ... @@ -1,21 +1,20 @@
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.
1 +During our recent sprint cycle, we have done many fixes. These are mainly related to flow testing, alerting, and the deploy phase. Apart from that, we have improved the tracing information for errorChannel messages, and added search functionality to the Start/Stop flows overview.
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.227 - Fix Frenzy||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Community - Release Notes: The legacy release notes tab has been removed.
7 -* Create - Flow Designer: The styling of the "File Item Reader Message Source" component configuration pop-up has been improved. (#1152)
8 -* Create - Flow Testing: Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
9 -* Deploy - Architecture: The SSL section in runtime settings has more elaborate helptext. (#1277)
10 -* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended. (#1423)
11 -* Deploy - Architecture: The helptext of volume mappings has been improved. (#1405)
12 -* Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.
13 -* Deploy - History: We added logging for when properties are deleted from the unused properties screen. (#1428)
14 -* 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)
15 -* 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)
6 +* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
7 +* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. (#1311)
8 +* Manage - Alerting: The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
16 16  
17 17  ====Bug fixes====
18 -* 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)
19 -* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392)
20 -* Create - Flow Testing: It is now possible to reuse the test messages created in other flows within the routing and vice versa. (#1274)
21 -* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)
11 +* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294)
12 +* Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
13 +* Create - Flow Testing: In case opening a log of test execution is not possible, a warning message will now be shown.
14 +* Create - Message Definitions: 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.
15 +* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379)
16 +* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release. This has been resolved.
17 +* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310)
18 +* Manage - Alerting: 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 test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
19 +* Manage - Alerting: 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.
20 +* Manage - Alerting: 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.