Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 369.1
edited by Carlijn Kokkeler
on 2024/01/29 15:37
on 2024/01/29 15:37
Change comment:
There is no comment for this version
To version 382.1
edited by Carlijn Kokkeler
on 2024/02/12 16:50
on 2024/02/12 16:50
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 -21 3-JoyfulJourneys1 +214 - System Symphony - Content
-
... ... @@ -3,78 +3,48 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release,several improvementsfor pop-ups have been made sothatmoreuser friendlymessagesareshownthatreflect actualbehaviour. Moreover,formattingandalignmentimprovementshavebeen made to improve theuserjourney. Lastly,wehaveworkedon some morefeedback items andseveral more bug fixes have been done.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. 7 7 8 -== ** Pop-upImprovements** ==8 +== **Feedback Items** == 9 9 10 -//__ Property releases__//11 -W hena new propertyreleaseiscreated, this propertyrelease cannownotonlybeviewedbut alsorelease propertiescanbedeleted.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 12 13 -[[image:Main.Images. Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]] 14 14 15 -//__ Runtime deletion__//16 - When deletinga runtime,the errormessage thatis displayedismore descriptive.Theerror messages willnowincludethenamesofthe flowsthat runon thecontainer.15 +//__Adding multiple attributes__// 16 +It is now possible to add multiple existing attributes to an entity at once. 17 17 18 -//__Wiretap & debug error messages__// 19 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 18 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]] 20 20 21 -//__ Actionmessages__//22 -The formattingof actionmessagesregardingchangesinretentionbytes/hourshas been improved. Theaction messagewillnowdisplaythecorrect,actualbehaviour.20 +//__Monitoring graphs__// 21 +The monitoring graphs can now show data up to the last thirty days. 23 23 24 -== **Formatting & Alignments** == 23 +== **Bug Fixes** == 24 +//__Image versions__// 25 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. 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. 25 25 26 -//__ Inputfields__//27 - Multipleinput fieldshavebeen updated suchthattheyexpand whentheamountof characters exceedsthe defaultsize.These updatesweredoneto cater to large expressions.27 +//__Failover group helptext__// 28 +The helptext of the Group attribute has been improved. 28 28 29 -//__UI improvements__// 30 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 30 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 31 31 32 -//__ Componentchangesreversion__//33 - In theflowdesignera bugcouldoccurwherethechangestoa componentwouldbe revertedif theediting pop-upwould bekeptopenforsomeminutes without havingsavedthe changesyet.Thishasbeenfixed.32 +//__Failover group refresh__// 33 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen. 34 34 35 -//__State generation statistics__// 36 -The state generation graphs will now show the correct number of cache hits and misses. 35 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 37 37 38 -//__ Queue browsertimestamps__//39 -A lltimestampformattingin thequeuebrowserisnowalignedtoyyyy-MM-ddHH:mm:ss.SSS.37 +//__Resource paths__// 38 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed. 40 40 41 -//__Addition and deletion of internal recipients__// 42 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 43 - 44 -== **Feedback Items** == 45 - 46 -//__Update flows__// 47 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 48 - 49 -//__Q&A forum search__// 50 -The option to search by pressing the Enter key has been added to the Q&A forum. 51 - 52 -//__Memory settings__// 53 -It is now possible to change the memory settings of a newly added container before pressing "Apply to environment". 54 -//__Runtime validation__// 55 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 56 - 57 -//__Runtime overview image versions__// 58 -Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 59 - 60 -== **Bug Fixes** == 61 - 62 -//__Removal of onramp__// 63 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 64 - 65 -//__Runtime statistics details__// 66 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 67 - 68 -//__Deployment prechecks__// 69 -During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture. 70 - 71 71 == **Fancy Forum Answers** == 72 72 73 73 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: 74 74 75 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 76 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 77 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 44 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 45 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 46 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 47 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]] 78 78 79 79 == **Key Takeaways** == 80 80