Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 259.1
edited by Carlijn Kokkeler
on 2024/06/05 09:30
Change comment: There is no comment for this version
To version 306.1
edited by Carlijn Kokkeler
on 2024/08/26 14:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +228 - Monitoring Mania
Content
... ... @@ -1,17 +1,19 @@
1 -In the last sprint cycle, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Find out about the rest 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.222 - Flee Frustration||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 -* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
5 +====Minor changes====
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.
9 +* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended.
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.
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.
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 -* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
10 -* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
11 -* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)4
12 -* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
13 -* Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
14 -* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
15 -
16 -
17 -
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 from the onramp in the routing and vice versa in flow testing. (#1274)
19 +* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)