Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 327.1
edited by Carlijn Kokkeler
on 2024/01/02 10:21
on 2024/01/02 10:21
Change comment:
There is no comment for this version
To version 543.1
edited by Carlijn Kokkeler
on 2024/06/03 13:23
on 2024/06/03 13:23
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 11-LogLuminary1 +222 - Flee Frustration - Content
-
... ... @@ -3,70 +3,47 @@ 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 havedone muchwork toimprove ourloggingand overviews.Thisshouldimproveheuser experiencefor ourplatform.Next to this,we have done severalminorchanges andbugfixes,mainlyrelating totheDeploy andManagephase.6 +**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to read about the details and the rest of our bug fixes! 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 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 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.jpg]] 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 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]] 44 44 45 -//__Broker queue metrics dashboards__// 46 -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. 47 47 48 -//__ Runtimeimageversion__//49 - 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. 50 50 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 51 51 52 -== **Bug Fixes** == 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 53 53 54 -//__ Messagethroughput__//55 - The message throughput graph intheManage phasewillnowshowthecorrectdata,independentfrom theselectedtime internal. Before,thisgraphwouldnotshow any datain some cases.31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 56 56 57 -//__ Cloudtemplate upgrade unjust rollback__//58 - An issuehasbeenfixed whereacloudtemplateupgradewould berolled back unjustly dueto failedruntimechecks.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 59 59 60 -//__Next generation block__// 61 -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]] 62 62 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"]] 43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 68 68 69 -== **Key takeaways** ==46 +== **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,10 +74,9 @@ 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] 54 +* 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 -* Upgrade to the latest build number 81 81 * Keep making great integrations 82 82 83 83 Let's stay in touch and till next time! ... ... @@ -85,7 +85,6 @@ 85 85 {{info}} 86 86 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 87 87 88 -~*~* Indicates a next-generation-architecture only feature. 89 89 {{/info}} 90 90 ))) 91 91