Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 548.1
edited by Carlijn Kokkeler
on 2024/06/03 16:00
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
Content
... ... @@ -6,11 +6,6 @@
6 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 7  
8 8  == **Feedback Items** ==
9 -//__Cron triggers__//
10 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
11 -
12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
13 -
14 14  //__Design changes__//
15 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 16  
... ... @@ -17,6 +17,11 @@
17 17  [[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
18 18  
19 19  == **Bug Fixes** ==
15 +//__Cron triggers__//
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
17 +
18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
19 +
20 20  //__Trigger activation__//
21 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.
22 22