Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
on 2024/01/15 14:14
Change comment:
There is no comment for this version
To version 541.1
edited by Carlijn Kokkeler
on 2024/06/03 13:13
on 2024/06/03 13:13
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 12 - FailoverFiesta1 +222 - Flee Frustration - Content
-
... ... @@ -3,43 +3,48 @@ 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 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. 9 9 10 -//__Failover setup__// 11 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]] 12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 12 12 13 -[[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. 14 14 15 -//__External recipients emailaddress__// 16 -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. 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 17 17 18 -//__Broker queue metrics dashboards__// 19 -It is now possible to select the MQTT broker in the queue metrics dashboards. 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 21 -//__ Runtimeimageversion__//22 - Theversionof runtime images used to prepareyourcontainersfor deploymentswill be the sameacross allenvironments.Thisholdsfor releases thataredeployedpromotedtoaextvironment.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. 23 23 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 24 24 25 -== **Bug Fixes** == 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 26 26 27 -//__ Messagethroughput__//28 - The message throughput graph intheManage phasewillnowshowthecorrectdata,independentfrom theselectedtime internal. Before,thisgraphwouldnotshow any datain some cases.31 +//__Invalid memory configurations__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 29 29 30 -//__ Cloudtemplateupgrade incorrect rollback__//31 - An issuehasbeenfixed whereacloudtemplateupgradewould be rolled back incorrectly dueto failedruntimechecks.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 32 32 33 -//__Next generation block__// 34 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 35 35 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 43 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 44 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 45 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 41 41 42 -== **Key takeaways** ==47 +== **Key Takeaways** == 43 43 44 44 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: 45 45 ... ... @@ -47,7 +47,7 @@ 47 47 * If you have feedback or ideas for us, talk to the Platypus 48 48 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 49 * Clear your browser cache (Ctrl + Shift + Del) 50 -* Check out the release notes [here] 55 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 51 51 * Start thinking about how the license tracker can aid your development 52 52 * Start thinking about major, minor, and patch 53 53 * Keep making great integrations