Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 553.1
edited by Carlijn Kokkeler
on 2024/06/17 12:27
Change comment: There is no comment for this version
To version 549.1
edited by Carlijn Kokkeler
on 2024/06/05 09:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - TBD
1 +222 - Flee Frustration
Content
... ... @@ -3,26 +3,39 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
7 -
6 +**Hi there, eMagiz developers!** This release, 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. Dive into our release blog to find out about the details and the rest of our bug fixes!
7 +
8 8  == **Feedback Items** ==
9 -//__SwaggerUI default__//
10 -Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
9 +//__Design changes__//
10 +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.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
12 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
13 13  
14 -//__SwaggerUI default__//
15 -We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
14 +== **Bug Fixes** ==
15 +//__Cron triggers__//
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
16 16  
18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
17 17  
20 +//__Trigger activation__//
21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
18 18  
19 -== **Bug Fixes** ==
20 -//__SFTP sessions__//
21 -Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
23 +//__Multiple users deploying__//
24 +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.
22 22  
23 -//__SFTP helptext//
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
24 24  
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
25 25  
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33 +
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
36 +
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
38 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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: