Changes for page 215 - Tiny Tales
Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
on 2024/02/12 15:09
Change comment:
There is no comment for this version
To version 276.1
edited by Carlijn Kokkeler
on 2023/12/04 14:43
on 2023/12/04 14:43
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-System Symphony1 +209 - Deployment Delights - Content
-
... ... @@ -3,45 +3,46 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Inthis release,...6 +**Hi there, eMagiz developers!** We have... 7 7 8 +== **Release Maintenance** == 9 + 10 + 11 + 12 + 13 + 8 8 == **Feedback Items** == 9 9 10 -//__ Updateflows__//11 - Support fordeployingtoonpremiseWindowsmachines has beendelivered.16 +//__Harbor port change__// 17 +The port for which you need to register has been changed ...? 12 12 13 -//__ Image versions__//14 - Thedeletionofreleaseswithdeployedcontainer versionswillnotbe blocked anymore. Automatedreleaseclean up behaviour will alsonot exclude thesereleases from deletion.Images thatbelongto deletedreleases willbekeptifthereare otherreleasesthat wouldreuse them,otherwisethey willbe deletedtogetherwiththe releases.19 +//__Container version overview__// 20 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 15 15 16 -//__Adding multiple attributes__// 17 -It is now possible to add multiple existing attributes to an entity at once. 22 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 18 18 19 -//__ Monitoring graphs__//20 - Themonitoringgraphs can nowshowdataupto the last30days.24 +//__Unchanged containers__// 25 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 21 21 22 -== **Bug Fixes** == 23 -//__Failover group helptext__// 24 -The helptext of the Group attribute has been improved. 27 +//__Rebuilding of images__// 28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 27 27 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. 31 +== **Bug Fixes** == 30 30 31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 33 +//__Runtime metrics processing__// 34 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 32 32 33 -//__ Resource paths__//34 - Aftermigratinga gatewaytoGen3,theathreferencesin the event processors wouldbe broken. This has beenfixed.36 +//__Deployment plan__// 37 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 35 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 -* [[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"]] 43 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 43 43 44 -== **Key Takeaways** ==45 +== **Key takeaways** == 45 45 46 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: 47 47 ... ... @@ -52,6 +52,7 @@ 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development 54 54 * Start thinking about major, minor, and patch 56 +* Upgrade to the latest build number 55 55 * Keep making great integrations 56 56 57 57 Let's stay in touch and till next time! ... ... @@ -59,6 +59,7 @@ 59 59 {{info}} 60 60 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 64 +~*~* Indicates a next-generation-architecture only feature. 62 62 {{/info}} 63 63 ))) 64 64