Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 350.2
edited by Carlijn Kokkeler
on 2024/01/29 13:22
Change comment: There is no comment for this version
To version 279.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
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,29 +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 -//__Property releases__//
12 -When a new property release is created, this property release can now be viewed and deleted.
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  
14 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
15 15  
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 +
16 16  == **Bug Fixes** ==
17 17  
30 +//__Runtime metrics processing__//
31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
18 18  
33 +//__Deployment plan__//
34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
19 19  
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 +
20 20  == **Fancy Forum Answers** ==
21 21  
22 22  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:
23 23  
24 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
25 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
26 -* [[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"]]
27 27  
28 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
29 29  
30 30  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:
31 31  
... ... @@ -36,6 +36,7 @@
36 36  * Check out the release notes [here]
37 37  * Start thinking about how the license tracker can aid your development
38 38  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
39 39  * Keep making great integrations
40 40  
41 41  Let's stay in touch and till next time!
... ... @@ -43,6 +43,7 @@
43 43  {{info}}
44 44  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
45 45  
74 +~*~* Indicates a next-generation-architecture only feature.
46 46  {{/info}}
47 47  )))
48 48