Skip to Content

Changes for page 224 - Summer Sonata

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +223 - TBD
Content
... ... @@ -4,21 +4,21 @@
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 6  **Hi there, eMagiz developers!**
7 -
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.
11 +
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
13 +
14 +== **Bug Fixes** ==
9 9  //__Cron triggers__//
10 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
11 11  
12 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 -
19 -== **Bug Fixes** ==
20 20  //__Trigger activation__//
21 -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.
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  
23 23  //__Multiple users deploying__//
24 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.
... ... @@ -28,7 +28,7 @@
28 28  //__Invalid memory configurations__//
29 29  We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30 30  
31 -//__Invalid memory configurations__//
31 +//__Property value synchronization__//
32 32  Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33 33  
34 34  //__JMS number__//
... ... @@ -51,7 +51,7 @@
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 52  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
57 57  * Keep making great integrations