Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 275.1
edited by Carlijn Kokkeler
on 2023/12/04 14:34
Change comment: There is no comment for this version
To version 373.1
edited by Carlijn Kokkeler
on 2024/02/12 15:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +214 - System Symphony
Content
... ... @@ -3,46 +3,42 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!** In this release, ...
7 7  
8 -== **Release Maintenance** ==
9 -
10 -
11 -
12 -
13 -
14 14  == **Feedback Items** ==
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
10 +//__Update flows__//
11 +Support for deploying to on premise Windows machines has been delivered.
18 18  
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.
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.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
16 +//__Adding multiple attributes__//
17 +It is now possible to add multiple existing attributes to an entity at once.
23 23  
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.
26 26  
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 29  
30 30  
31 31  == **Bug Fixes** ==
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
32 32  
33 -//__Runtime metrics processing__//
34 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
35 35  
36 -//__Deployment plan__//
37 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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.
38 38  
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
32 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
44 44  
45 -== **Key takeaways** ==
41 +== **Key Takeaways** ==
46 46  
47 47  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:
48 48  
... ... @@ -53,7 +53,6 @@
53 53  * Check out the release notes [here]
54 54  * Start thinking about how the license tracker can aid your development
55 55  * Start thinking about major, minor, and patch
56 -* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,7 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a next-generation-architecture only feature.
65 65  {{/info}}
66 66  )))
67 67