Changes for page 215 - Tiny Tales
Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 396.1
edited by Carlijn Kokkeler
on 2024/02/26 10:38
on 2024/02/26 10:38
Change comment:
There is no comment for this version
To version 284.1
edited by Carlijn Kokkeler
on 2023/12/04 15:20
on 2023/12/04 15: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 5-TinyTales1 +210 - Deployment Delights - Content
-
... ... @@ -3,35 +3,56 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This releaseblog isasmall one,because wehavebeenbusyworkingonitems that will bereleased later on.Forthis release, the event streaminggraph ahs beenimproved.Moreover,somebug fixeshave beendone,regardingqueuenamevalidation, theremovalofnrampspreviouslylinkedtoacombinedentry,and logginginto eMagizby pressingenter when havingtheusernamefieldselected.6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several 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’ alert 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 -//__Improved event streaming graph__// 10 -The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics.png]] 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. 13 13 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 22 + 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. 25 + 26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 28 + 14 14 == **Bug Fixes** == 15 -//__Queue name validation__// 16 -The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name. 17 17 18 -//__Rem ovalof onramp__//19 - Anissuehasbeen fixedwhereitwas notpossibletoremove anonrampthatwaspreviouslylinkedtoacombined entry.31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 20 20 21 -//__e Magizlogin__//22 - In theloginscreen,usersnowavethe abilitytopress enterto log in whenhavingtheusernamefieldselected. Previouslythis was onlythecase forthepassword field.34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 23 23 37 +//__Store message merging__// 38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 39 + 40 +//__View all store items__// 41 +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. 42 + 43 +//__Out of memory behavior__// 44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 45 + 46 +//__Max fetch size__// 47 +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. 48 + 24 24 == **Fancy Forum Answers** == 25 25 26 26 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: 27 27 28 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 29 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 30 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 31 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 32 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 33 33 34 -== **Key Takeaways** ==55 +== **Key takeaways** == 35 35 36 36 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: 37 37 ... ... @@ -42,6 +42,7 @@ 42 42 * Check out the release notes [here] 43 43 * Start thinking about how the license tracker can aid your development 44 44 * Start thinking about major, minor, and patch 66 +* Upgrade to the latest build number 45 45 * Keep making great integrations 46 46 47 47 Let's stay in touch and till next time! ... ... @@ -49,6 +49,7 @@ 49 49 {{info}} 50 50 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 51 51 74 +~*~* Indicates a next-generation-architecture only feature. 52 52 {{/info}} 53 53 ))) 54 54