Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 540.1
edited by Carlijn Kokkeler
on 2024/06/03 13:04
Change comment: There is no comment for this version
To version 592.1
edited by Carlijn Kokkeler
on 2024/07/16 11:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +225 - TBD
Content
... ... @@ -5,36 +5,27 @@
5 5  
6 6  **Hi there, eMagiz developers!**
7 7  
8 +
8 8  == **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 +//__Alerting notification settings__//
11 +The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
13 +[[image:Main.Images.Release Blog.WebHome@release-225-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.
15 +//__Process containers__//
16 +If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
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.
22 22  
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.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
27 27  
28 -//__Invalid memory configurations__//
29 -We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30 30  
23 +
31 31  == **Fancy Forum Answers** ==
32 32  
33 33  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:
34 34  
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"]]
28 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
38 38  
39 39  == **Key Takeaways** ==
40 40  
... ... @@ -44,7 +44,7 @@
44 44  * If you have feedback or ideas for us, talk to the Platypus
45 45  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46 46  * Clear your browser cache (Ctrl + Shift + Del)
47 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
38 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
48 48  * Start thinking about how the license tracker can aid your development
49 49  * Start thinking about major, minor, and patch
50 50  * Keep making great integrations