Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 279.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
Change comment: There is no comment for this version
To version 350.2
edited by Carlijn Kokkeler
on 2024/01/29 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +213 - Joyful Journeys
Content
... ... @@ -3,56 +3,29 @@
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!** This release ....
7 7  
8 -== **Release Maintenance** ==
9 9  
10 -
11 -
12 -
13 -
14 14  == **Feedback Items** ==
15 15  
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.
11 +//__Property releases__//
12 +When a new property release is created, this property release can now be viewed and deleted.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
14 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
20 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 -
28 28  == **Bug Fixes** ==
29 29  
30 -//__Runtime metrics processing__//
31 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
32 32  
33 -//__Deployment plan__//
34 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 35  
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 -
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
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"]]
54 54  
55 -== **Key takeaways** ==
28 +== **Key Takeaways** ==
56 56  
57 57  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:
58 58  
... ... @@ -63,7 +63,6 @@
63 63  * Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
65 65  * Start thinking about major, minor, and patch
66 -* Upgrade to the latest build number
67 67  * Keep making great integrations
68 68  
69 69  Let's stay in touch and till next time!
... ... @@ -71,7 +71,6 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 -~*~* Indicates a next-generation-architecture only feature.
75 75  {{/info}}
76 76  )))
77 77