Skip to Content

Changes for page 224 - Summer Sonata

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +222 - Flee Frustration
Content
... ... @@ -3,70 +3,38 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
11 -
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container.
14 -
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
17 -
18 -== **Overviews** ==
19 -
20 -//__Runtime overview__//
21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
24 -
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
29 -
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
32 -
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 -
35 35  == **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.
36 36  
37 -//__Breaking changes pop-up__//
38 -The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.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.
41 41  
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
44 -
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
47 -
48 -//__Runtime image version__//
49 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
50 -
51 -
52 52  == **Bug Fixes** ==
18 +//__Trigger activation__//
19 +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.
53 53  
54 -//__Message throughput__//
55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
21 +//__Multiple users deploying__//
22 +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.
56 56  
57 -//__Cloud template upgrade incorrect rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
24 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
59 59  
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 62  
27 +We have resolved deprecated warnings as part of our preparation to upgrade to Mendix version 10.
28 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
33 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
34 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
35 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
68 68  
69 -== **Key takeaways** ==
37 +== **Key Takeaways** ==
70 70  
71 71  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
72 72  
... ... @@ -74,7 +74,7 @@
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 75  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 -* Check out the release notes [here]
45 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 80  * Keep making great integrations