Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
on 2023/05/22 14:03
Change comment:
There is no comment for this version
To version 411.1
edited by CarlijnKokkeler
on 2024/03/25 10:35
on 2024/03/25 10:35
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 98-GreatMigration1 +217 - Template Tango - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,60 +1,56 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** 3rdgenerationimprovementsandbugfixes** ==8 +== **Cloud Template R12 Docker - Single Lane** == 8 8 9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__// 10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed. 10 +== **Cloud Template R14 Docker - Double Lane** == 11 11 12 -{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}} 12 +== **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. 13 13 14 -//__Removed certain dependencies between Deploy Architecture and Releases__// 15 -In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release. 16 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]] 16 16 17 -//__ Improved validationerrorsoninvalid configurationof HTTP outboundcomponents__//18 - Thisreleasefixes andre-introducestheoptiontoexecuteyour actionson theeMagizperzone orall at oncewhenrunningina double-laneDocker setup.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. 19 19 20 -//__Improved migration behavior__// 21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished. 21 +== **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. 22 22 23 -//__Improved auto-healing when running in a hybrid situation__// 24 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture. 25 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 25 25 26 -//__ Improved rollupand storage ofmetrics when running your solutionin the next generation archticture__//27 - Toimprove thestability of theManage phaseand,in particular, themetricswhenzoomingouton theprovidedinformation,we havemade somestructuralchangesthat support thisuserfunctionalitybetter.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. 28 28 29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}} 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. 30 30 31 -== **Feedback items ** == 32 - 33 -//__Make sure the message format can be viewed without "Start editing"__// 34 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode. 35 - 36 -//__Various styling improvements in the flow testing functionality__// 37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details. 38 - 39 39 == **Fancy Forum Answers** == 40 40 41 41 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: 42 42 43 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]] 44 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||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"]] 45 45 46 -== **Key takeaways** ==43 +== **Key Takeaways** == 47 47 48 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:45 +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: 49 49 50 50 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 51 51 * If you have feedback or ideas for us, talk to the Platypus 52 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 53 53 * Clear your browser cache (Ctrl + Shift + Del) 54 54 * Check out the release notes [here] 55 55 * Start thinking about how the license tracker can aid your development 56 56 * Start thinking about major, minor, and patch 57 -* Upgrade to the latest build number 58 58 * Keep making great integrations 59 59 60 60 Let's stay in touch and till next time! ... ... @@ -62,6 +62,11 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -~*~* Indicates a GEN3-only feature. 66 -{{/info}})))((({{toc/}}))){{/container}} 61 +{{/info}} 62 +))) 63 + 64 +((( 65 +{{toc/}} 66 +))) 67 67 {{/container}} 68 +{{/container}}