Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

From version 349.1
edited by Carlijn Kokkeler
on 2024/01/29 12:56
Change comment: There is no comment for this version
To version 280.1
edited by Carlijn Kokkeler
on 2023/12/04 15:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +209 - Deployment Delights
Content
... ... @@ -3,27 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
6 +**Hi there, eMagiz developers!** We have...
7 7  
8 +== **Release Maintenance** ==
8 8  
10 +
11 +
12 +
13 +
9 9  == **Feedback Items** ==
10 10  
11 -//__Failover setup__//
12 -New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
16 +//__Container version overview__//
17 +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 13  
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
20 +
21 +//__Unchanged containers__//
22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 +
24 +//__Rebuilding of images__//
25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26 +
27 +
14 14  == **Bug Fixes** ==
15 15  
30 +//__Runtime metrics processing__//
31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
16 16  
33 +//__Deployment plan__//
34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
17 17  
36 +//__Store message merging__//
37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
38 +
39 +//__View all store items__//
40 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
41 +
42 +//__Out of memory behavior__//
43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 +
45 +//__Max fetch size__//
46 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
47 +
48 +
18 18  == **Fancy Forum Answers** ==
19 19  
20 20  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:
21 21  
22 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
23 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
24 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
25 25  
26 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
27 27  
28 28  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:
29 29  
... ... @@ -34,6 +34,7 @@
34 34  * Check out the release notes [here]
35 35  * Start thinking about how the license tracker can aid your development
36 36  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
37 37  * Keep making great integrations
38 38  
39 39  Let's stay in touch and till next time!
... ... @@ -41,6 +41,7 @@
41 41  {{info}}
42 42  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
43 43  
74 +~*~* Indicates a next-generation-architecture only feature.
44 44  {{/info}}
45 45  )))
46 46