Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 536.1
edited by Carlijn Kokkeler
on 2024/06/03 12:15
Change comment: There is no comment for this version
To version 541.1
edited by Carlijn Kokkeler
on 2024/06/03 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,20 +6,36 @@
6 6  **Hi there, eMagiz developers!**
7 7  
8 8  == **Feedback Items** ==
9 -//__Trigger activation__//
9 +//__Cron triggers__//
10 10  Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
13 13  
14 +//__Design changes__//
15 +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.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
18 +
14 14  == **Bug Fixes** ==
15 15  //__Trigger activation__//
16 16  Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
17 17  
18 -//__Trigger activation__//
23 +//__Multiple users deploying__//
19 19  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.
20 -
21 21  
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
22 22  
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30 +
31 +//__Invalid memory configurations__//
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 +
23 23  == **Fancy Forum Answers** ==
24 24  
25 25  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: