Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 429.1
edited by CarlijnKokkeler
on 2024/03/25 16:44
on 2024/03/25 16:44
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 217-TemplateTango1 +198 - Great Migration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,71 +1,60 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In th is release,newcloudtemplatesfordockersingle anddockerdoublelaneareintroduced.Thesetemplatesenabletheability to cleanH2 databasesfromtheportal.Next to this, it is nowpossible to edit thetrigger"Morethan100 messagesonqueueover 10 minutes". Moroever, serveralcopy to clipboard buttons have been added.Lastly,theruntime overviewhasbeenimproved with respecttochecksontheruntimeversion.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. 7 7 8 - {{info}}Reminder! Asannouncedin ourprevious [[release blog>>Main.ReleaseInformation.ReleaseBlogs.216- Hack Heaven||target="blank"]], with thereleaseof the 11th of April:7 +== **3rd generation improvements and bug fixes** == 9 9 10 - * TLSv1.0andTLSv1.1willbedeprecated.11 - * A majorversionof our[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]base imageforallourclients runningonthe**[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]**architecturewillbereleased.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. 12 12 13 - For more information,pleasecheckoutour [[release blog>>Main.ReleaseInformation.ReleaseBlogs.216-Hack Heaven||target="blank"]]from the previous release.{{/info}}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}} 14 14 15 - == **CloudTemplateR12Docker- SingleLane** ==16 - This releaseintroducesanewnon-serviceaffecting cloudtemplateforallour customers runningina single-lanesetup.This cloudtemplateintroducestheabilityto cleanH2 databasesfromtheportal. The completereleasenotesonthe cloudtemplatecanbefound[[here>>doc:Main.ReleaseInformation.CloudTemplates.R12 Docker - SingleLane.WebHome||target="blank"]].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. 17 17 18 - == **CloudTemplateR14 Docker-DoubleLane** ==19 -This release i ntroduces anewnon-serviceaffecting cloudtemplate forallourcustomersrunning in a single-lane setup. Thiscloud templateintroducestheabilitytoclean H2 databasesfromtheportal.The completereleasenotes onthecloudtemplatecanbefound[[here>>doc:Main.ReleaseInformation.Cloud Templates.R14Docker- DoubleLane.WebHome||target="blank"]].17 +//__Improved validation errors on invalid configuration of HTTP outbound components__// 18 +This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup. 20 20 21 -== **Feedback Items** == 22 -//__Dynamic trigger__// 23 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger. 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 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. 26 26 27 -//__ Copyto clipboardbuttons__//28 - Copytoclipboardbuttonshavebeenaddedtovariouspages:26 +//__Improved rollup and storage of metrics when running your solution in the next generation archticture__// 27 +To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better. 29 29 30 - * Deploy agent pop-up 31 - * Create - Flow designer: Properties 32 - * Deploy - Property releases: Property details 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}} 33 33 34 - [[image:Main.Images.ReleaseBlog.WebHome@release-217-template-tango-copy-to-clipboard.png]]31 +== **Feedback items ** == 35 35 36 -//__ ResetH2database__//37 - For our **[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture,itisnowpossibletoremove the eMagizinfraH2 databaseforconnectormachines.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. 38 38 39 -{{info}}Please note the following: 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. 40 40 41 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 42 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. 43 -* For on-premise runtimes, only a reset of the runtime is needed.{{/info}} 44 - 45 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 46 - 47 -== **Bug Fixes** == 48 -//__Runtime overview improvements__// 49 -The runtime overview has been improved regarding checks on the runtime version. 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 -* [[ XSD is onlypartiallyimportedintoeMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]56 -* [[ TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]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"]] 57 57 58 -== **Key Takeaways** ==46 +== **Key takeaways** == 59 59 60 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:48 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 61 61 62 62 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 63 63 * If you have feedback or ideas for us, talk to the Platypus 64 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 65 65 * Clear your browser cache (Ctrl + Shift + Del) 66 66 * Check out the release notes [here] 67 67 * Start thinking about how the license tracker can aid your development 68 68 * Start thinking about major, minor, and patch 57 +* 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,11 +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 -{{/info}} 77 -))) 78 - 79 -((( 80 -{{toc/}} 81 -))) 65 +~*~* Indicates a GEN3-only feature. 66 +{{/info}})))((({{toc/}}))){{/container}} 82 82 {{/container}} 83 -{{/container}}