Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 391.1
edited by Carlijn Kokkeler
on 2024/02/14 10:10
on 2024/02/14 10:10
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 14-SystemSymphony1 +222 - Flee Frustration - Content
-
... ... @@ -3,52 +3,46 @@ 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, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 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 -We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 12 12 13 - [[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]14 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-214-system-symphony-windows.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. 15 15 16 -//__Adding multiple attributes__// 17 -It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 18 18 19 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]] 20 - 21 -//__Monitoring graphs__// 22 -The monitoring graphs can now show data up to the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 23 - 24 24 == **Bug Fixes** == 25 -//__Image versions__// 26 -To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way: 27 -* The deletion of releases with deployed container versions will not be blocked anymore. 28 -* Automated release clean up behaviour will also not exclude these releases from deletion. 29 -* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases. 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. 30 30 31 -//__ Failovergrouphelptext__//32 - 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. 33 33 34 -[[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]] 35 35 36 -//__ Failovergrouprefresh__//37 - A newstate'Leader(singlenode)'has beenaddedincasethereisonlyonenode forfailover setup.Moreover,arefresh buttonisaddedin theGroup tabof "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. 38 38 39 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 31 +//__Invalid memory configurations__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 40 40 41 -//__ Resourcepaths__//42 - Aftermigratinga gateway away fomthelegacyruntimearchitecture,thepath referencesintheeventprocessorswould bebroken. Thishas beenfixed.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 43 43 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 38 + 44 44 == **Fancy Forum Answers** == 45 45 46 46 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: 47 47 48 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 49 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 50 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 51 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||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"]] 52 52 53 53 == **Key Takeaways** == 54 54 ... ... @@ -58,7 +58,7 @@ 58 58 * If you have feedback or ideas for us, talk to the Platypus 59 59 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 60 60 * Clear your browser cache (Ctrl + Shift + Del) 61 -* Check out the release notes [here] 55 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 62 62 * Start thinking about how the license tracker can aid your development 63 63 * Start thinking about major, minor, and patch 64 64 * Keep making great integrations