Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 154.1
edited by Carlijn Kokkeler
on 2023/10/10 13:41
on 2023/10/10 13:41
Change comment:
There is no comment for this version
To version 373.1
edited by Carlijn Kokkeler
on 2024/02/12 15:03
on 2024/02/12 15:03
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 06- Situational Deployment1 +214 - System Symphony - Content
-
... ... @@ -1,50 +1,44 @@ 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 th e lastfew weeks, we have done much work for theDeploy phase. On top of that, we have worked onseveral store functionalities. Next to this,we have several smaller feedback items from our hackathon efforts that are now released to you.6 +**Hi there, eMagiz developers!** In this release, ... 6 6 7 -== ** Deployment Plan** ==8 +== **Feedback Items** == 8 8 9 -//__ Improveddeployment planto makethe process better and more predictable__//10 - The algorithmforgenarating adefault deploymentplanis improved to keep jms downtimeand alerting toa minimum. Next to this,the start/stop/restartmachinedeploymentstepsare now alsoexecuted correctly for aws andon-premises machines.10 +//__Update flows__// 11 +Support for deploying to on premise Windows machines has been delivered. 11 11 12 -//__ Editingreleaseproperties__//13 - With thisrelease,it will bepossible to change thedescription ofa property byediting theproperty.13 +//__Image versions__// 14 +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. 14 14 16 +//__Adding multiple attributes__// 17 +It is now possible to add multiple existing attributes to an entity at once. 15 15 16 - 17 - 18 -== **Store Improvements** == 19 - 20 20 21 -== **Feedback Items** == 22 22 23 -//__Alerting manual pause__// 24 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 25 25 26 -//__Ordering of graphs in Manage__// 27 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 28 - 29 - 30 30 == **Bug Fixes** == 23 +//__Failover group helptext__// 24 +The helptext of the Group attribute has been improved. 31 31 32 -//__Gain the ability again to configure certificates in Deploy Architecture again__// 33 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. 26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 34 34 35 -//__ Ensure that differing containerconfigurations deploythe correct configuration__//36 - Whenyou runinamulti-runtimeconfigurationandchangethe actual flows that needtorunoncontainerA vs. container B, it happenedbeforethat all flows werestillbeing deployedonallruntimes. With thisrelease, we will feedthis informationcorrectly toourinfrastructuretoensurethe correctand configuredflowsaredeployed onthe proper containers.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. 37 37 38 -//__Remove queurying options in Manage__// 39 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors. 31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 40 40 41 41 == **Fancy Forum Answers** == 42 42 43 43 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: 44 44 45 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 37 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 38 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 39 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 46 46 47 -== **Key takeaways** ==41 +== **Key Takeaways** == 48 48 49 49 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: 50 50 ... ... @@ -55,7 +55,6 @@ 55 55 * Check out the release notes [here] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 58 -* Upgrade to the latest build number 59 59 * Keep making great integrations 60 60 61 61 Let's stay in touch and till next time! ... ... @@ -63,6 +63,11 @@ 63 63 {{info}} 64 64 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 65 66 -~*~* Indicates a next-generation-architecture only feature. 67 -{{/info}})))((({{toc/}}))){{/container}} 59 +{{/info}} 60 +))) 61 + 62 +((( 63 +{{toc/}} 64 +))) 68 68 {{/container}} 66 +{{/container}}