Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 353.1
edited by Carlijn Kokkeler
on 2024/01/29 13:37
Change comment: There is no comment for this version
To version 540.1
edited by Carlijn Kokkeler
on 2024/06/03 13:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +222 - Flee Frustration
Content
... ... @@ -3,30 +3,38 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
6 +**Hi there, eMagiz developers!**
7 7  
8 -
9 9  == **Feedback Items** ==
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.
10 10  
11 -//__Property releases__//
12 -When a new property release is created, this property release can now be viewed and deleted.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
15 15  
16 -//__Runtime deletion__//
17 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
18 18  
19 19  == **Bug Fixes** ==
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.
20 20  
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.
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 +
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:
26 26  
27 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
28 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
29 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
35 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
36 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
37 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
30 30  
31 31  == **Key Takeaways** ==
32 32  
... ... @@ -36,7 +36,7 @@
36 36  * If you have feedback or ideas for us, talk to the Platypus
37 37  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 38  * Clear your browser cache (Ctrl + Shift + Del)
39 -* Check out the release notes [here]
47 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
40 40  * Start thinking about how the license tracker can aid your development
41 41  * Start thinking about major, minor, and patch
42 42  * Keep making great integrations