Skip to Content

Changes for page 235 - Last Log

Last modified by Carlijn Kokkeler on 2024/12/04 14:02
From version 349.1
edited by Carlijn Kokkeler
on 2024/12/02 11:38
Change comment: There is no comment for this version
To version 260.1
edited by Bouke Reitsma
on 2024/06/06 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - Last Log
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.BoukeReitsma
Content
... ... @@ -1,16 +1,17 @@
1 -In this release, our new log alerting will be available! Please find out more about it **LINK**. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
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!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Manage - Alerting: We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well. Please check out our [[release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]] for the migration actions, and our new **ML LINK** about the design.
7 -* Manage - Alerting: We have improved the visibility of titles of larger columns in the new Alerting page.
8 -* Create - Flow Designer: Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:
9 -** It is now possible to add a local filter to the SMB inbound channel adapter.
10 -** It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adaptor, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.
11 -* All: We no longer support our legacy Mendix connector (< version 4.x).
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.
12 12  
13 13  ====Bug fixes====
14 -* Design - Flow Designer: The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode. (#1381)
15 -* Design - Flow Testing: The error that is sometimes thrown while switching between traces in flowtester is fixed. (#1521)
16 -* Deploy - Releases: The performance of selecting a runtime when editing properties in Deploy has been improved. (#1124)
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)
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 +