Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 126.1
edited by Erik Bakker
on 2023/06/19 14:24
on 2023/06/19 14:24
Change comment:
There is no comment for this version
To version 375.1
edited by Carlijn Kokkeler
on 2024/02/12 15:14
on 2024/02/12 15:14
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 00-UnchartedTerritories1 +214 - System Symphony - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,57 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In thelastfewweeks, wehaveworkedhardonalotf thingsthatare unfortanetly notquitereadytobereleased.Asa result theouputofthisrelease islimited. Havingsaidthatwestillbring somekeyimprovements intheDeploy andManagephasethatwould makelifemuch easier.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 30 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 6 7 -== ** Next generationimprovementsand bug fixes** ==8 +== **Feedback Items** == 8 8 9 -//__ Enhancedright-hand viewwithinDeploymentPlancontext__//10 - When executingyour deploymentplan we will showspecific log entriesof the infocategory that indicate that a container(i.e. runtime)hasstarted up correctly. Ontop of that we show the warnings andrrorsin this overview.10 +//__On premise Windows machines__// 11 +Support for deploying to on premise Windows machines has been delivered. 11 11 12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 13 +//__Adding multiple attributes__// 14 +It is now possible to add multiple existing attributes to an entity at once. 13 13 14 -//__ Improved timeoutsettingswhen deploying__//15 -T o avoid mismatchesbetweenvarious partsof theinfrastructure we have improved thetimeoutconfigurationoncertaindeploymentplanstepstoreducethechancethatthesemismatchesoccur.16 +//__Monitoring graphs__// 17 +The monitoring graphs can now show data up to the last 30 days. 16 16 17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 18 - 19 -//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 21 - 22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 23 - 24 -//__Improved loading speed of Manage Dashboard__// 25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 26 - 27 -== **Store Improvements** == 28 - 29 -//__Importing in Design is improved__// 30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 31 - 32 32 == **Bug Fixes** == 20 +//__Image versions__// 21 +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. 33 33 34 -//__ Deprecated reminderpop-upremoved__//35 - We haveremoveda reminderpop-uponapending cloudtemplate asitwas deprecatedand could causeissues whenusing it in communication with other systems.23 +//__Failover group helptext__// 24 +The helptext of the Group attribute has been improved. 36 36 37 -//__Improved selection area in Flow Designer__// 38 -When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow. 26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 39 39 40 -//__ ImprovedKafkasettings__//41 - Forall flowsthatusea Kafka relatedcomponentwithintheflowdesignerwewill run amigrationtoupdateeverysingle onef themtothenewbestpractices andcreateanew flowversionforthem.28 +//__Failover group refresh__// 29 +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. 42 42 43 - {{info}}We stronly encouragell users that usethesecomponents to updatetothese newbest practices as they increasestabilityof the cluster and throughput oftheolution{{/info}}31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 44 44 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 + 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 40 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 41 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 42 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 51 51 52 -== **Key takeaways** ==44 +== **Key Takeaways** == 53 53 54 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:46 +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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 60 * Check out the release notes [here] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 73 73 {{/container}} 69 +{{/container}}