Changes for page 215 - Tiny Tales
Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 376.1
edited by Carlijn Kokkeler
on 2024/02/12 15:17
on 2024/02/12 15:17
Change comment:
There is no comment for this version
To version 289.1
edited by Carlijn Kokkeler
on 2023/12/06 13:20
on 2023/12/06 13:20
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 -21 4-System Symphony1 +210 - Deployment Delights - Content
-
... ... @@ -3,47 +3,59 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This releasecontainsmultiplebugfixes, as well as someotherimprovements.Themonitoringgraphshavebeenimproved,suchthat theycan nowshow dataupto the last30days.Moreover,supportfor deploying to on premiseWindowsmachines is now available.Furthermore,severalimprovementsregarding failoverfunctionalityhavebeen done. Lastly,bug fixesregarding resourcepathsand imageversionshavebeendone.6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving. 7 7 8 +== **Alerts** == 9 + 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives. 12 + 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 15 + 8 8 == **Feedback Items** == 9 9 10 -//__ OnpremiseWindowsmachines__//11 - Supportfor deploying toonpremiseWindowsmachines hasbeendelivered.18 +//__Container version overview__// 19 +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. By having this overview, you can check which versions of the containers that exist in Deploy Architecture are in the release. 12 12 13 -//__Adding multiple attributes__// 14 -It is now possible to add multiple existing attributes to an entity at once. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 15 15 16 -//__ Monitoring graphs__//17 - Themonitoringgraphs can nowshow datauptohe last30days.23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. This decreases the deployment time and improves the performance. 18 18 26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 28 + 19 19 == **Bug Fixes** == 20 -//__Image versions__// 21 -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. 22 22 23 -//__ Failovergroup helptext__//24 -The helptext of theGroupattributehasbeen improved.31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 27 27 28 -//__ Failovergrouprefresh__//29 -A ewstate 'Leader (singlenode)'has beenaddedin case there isonlyonenodeforfailover setup. Moreover,a refreshbuttonisaddedinGrouptabof "Start/Stop Flows"screen.37 +//__View all store items__// 38 +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. 30 30 31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 40 +//__Out of memory behavior__// 41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 32 32 33 -//__ Resource paths__//34 - Aftermigrating a gatewaytoGen3,thepathreferencesin the eventprocessorswouldbebroken.Thishasbeenfixed.43 +//__Max fetch size__// 44 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 35 35 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 41 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 42 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 43 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]] 50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 44 44 45 -== **Key Takeaways** == 46 46 57 +== **Key takeaways** == 58 + 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 49 49 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -53,6 +53,7 @@ 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 68 +* Upgrade to the latest build number 56 56 * Keep making great integrations 57 57 58 58 Let's stay in touch and till next time! ... ... @@ -60,6 +60,7 @@ 60 60 {{info}} 61 61 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 62 62 76 +~*~* Indicates a next-generation-architecture only feature. 63 63 {{/info}} 64 64 ))) 65 65