Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 336.1
edited by Carlijn Kokkeler
on 2024/01/15 14:15
on 2024/01/15 14:15
Change comment:
There is no comment for this version
To version 280.1
edited by Carlijn Kokkeler
on 2023/12/04 15:00
on 2023/12/04 15:00
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 12-FailoverFiesta1 +209 - Deployment Delights - Content
-
... ... @@ -3,23 +3,54 @@ 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** == 9 + 10 + 11 + 12 + 13 + 8 8 == **Feedback Items** == 9 9 10 -//__ Failover setup__//11 - Newcomponentshavebeen createdtosupporta failoversetup.Moreinformationcan befound[[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. 12 12 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 13 13 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 -* [[Sa veheaderasclass 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 23 23 24 24 == **Key takeaways** == 25 25 ... ... @@ -32,6 +32,7 @@ 32 32 * Check out the release notes [here] 33 33 * Start thinking about how the license tracker can aid your development 34 34 * Start thinking about major, minor, and patch 66 +* Upgrade to the latest build number 35 35 * Keep making great integrations 36 36 37 37 Let's stay in touch and till next time! ... ... @@ -39,6 +39,7 @@ 39 39 {{info}} 40 40 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 41 41 74 +~*~* Indicates a next-generation-architecture only feature. 42 42 {{/info}} 43 43 ))) 44 44