Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 378.1
edited by Carlijn Kokkeler
on 2024/02/12 16:35
on 2024/02/12 16:35
Change comment:
There is no comment for this version
To version 540.1
edited by Carlijn Kokkeler
on 2024/06/03 13:04
on 2024/06/03 13:04
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 14-SystemSymphony1 +222 - Flee Frustration - Content
-
... ... @@ -3,44 +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 contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, support for deploying to on premise Windows machines is now available. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.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 -//__On premise Windows machines__// 11 -Support for deploying to on premise Windows machines has been delivered. 12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 12 12 13 -//__ Addingmultipleattributes__//14 -I tis nowpossibletoaddmultipleexistingattributestoanentityatonce.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 -//__Monitoring graphs__// 17 -The monitoring graphs can now show data up to the last thirty days. 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 18 18 19 19 == **Bug Fixes** == 20 -//__ Image versions__//21 - Thedeletion ofreleaseswith deployedcontainerversionswill notbeblockedanymore.Automatedreleasecleanupbehaviourwillalsonotexclude thesereleasesfromdeletion. Imagesthatbelong todeletedreleases willbekeptifthere areotherreleasesthatwould reuse them, otherwisetheywill bedeleted togetherwiththereleases.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 -//__ Failovergrouphelptext__//24 - Thehelptext oftheGroupattributehasbeenproved.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- blog-214-system-symphony-group-helptext.png]]26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 27 27 28 -//__ Failovergrouprefresh__//29 - A newstate'Leader(singlenode)'has beenaddedincasethereisonlyonenode forfailover setup.Moreover,arefresh buttonisaddedinGrouptabof "Start/StopFlows" screen.28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 30 30 31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 32 - 33 -//__Resource paths__// 34 -After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed. 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 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 41 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 42 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 43 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||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"]] 44 44 45 45 == **Key Takeaways** == 46 46 ... ... @@ -50,7 +50,7 @@ 50 50 * If you have feedback or ideas for us, talk to the Platypus 51 51 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 52 52 * Clear your browser cache (Ctrl + Shift + Del) 53 -* Check out the release notes [here] 47 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 54 54 * Start thinking about how the license tracker can aid your development 55 55 * Start thinking about major, minor, and patch 56 56 * Keep making great integrations