Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 281.2
edited by Carlijn Kokkeler
on 2023/12/04 15:08
on 2023/12/04 15:08
Change comment:
Update document after refactoring.
To version 410.1
edited by Carlijn Kokkeler
on 2024/03/25 10:30
on 2024/03/25 10:30
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 0-DeploymentDelights1 +217 - Template Tango - Content
-
... ... @@ -3,58 +3,44 @@ 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!** 7 7 8 -== ** Alerts** ==8 +== **Cloud Template R12 Docker - Single Lane** == 9 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. 10 +== **Cloud Template R12 Docker - Single Lane** == 12 12 13 -//__Missing metrics alert__// 14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 15 - 16 16 == **Feedback Items** == 13 +//__Improved event streaming graph__// 14 +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. 17 17 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. 16 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]] 20 20 21 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 18 +//__Flow versions auto deletion__// 19 +Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. 22 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 - 29 - 30 30 == **Bug Fixes** == 22 +//__Queue name validation__// 23 +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 when editing this in the Create phase in the Flow Designer. 31 31 32 -//__Runtime metrics processing__// 33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 25 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 34 34 35 -//__ Deploymentplan__//36 - Wesolveda bugwherea deploymentstepin thedeploymentplancould randomlyget stuck.27 +//__Removal of onramp__// 28 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase. 37 37 38 -//__ Storemessagemerging__//39 - Themessagemergingtoolhasbeenfixedtoallow mergingofyouragefinitionsfromtheStoretoexistingdata modelmessages.30 +//__eMagiz login__// 31 +In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field. 40 40 41 -//__View all store items__// 42 -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. 43 - 44 -//__Out of memory behavior__// 45 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 46 - 47 -//__Max fetch size__// 48 -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. 49 - 50 - 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 37 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 38 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 39 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 40 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 41 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 56 56 57 -== **Key takeaways** ==43 +== **Key Takeaways** == 58 58 59 59 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: 60 60 ... ... @@ -65,7 +65,6 @@ 65 65 * Check out the release notes [here] 66 66 * Start thinking about how the license tracker can aid your development 67 67 * Start thinking about major, minor, and patch 68 -* Upgrade to the latest build number 69 69 * Keep making great integrations 70 70 71 71 Let's stay in touch and till next time! ... ... @@ -73,7 +73,6 @@ 73 73 {{info}} 74 74 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 76 -~*~* Indicates a next-generation-architecture only feature. 77 77 {{/info}} 78 78 ))) 79 79