Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 431.1
edited by Erik Bakker
on 2024/03/26 14:08
on 2024/03/26 14:08
Change comment:
There is no comment for this version
To version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
on 2023/06/05 14:27
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 - 217-TemplateTango1 +199 - Home Improvements - Content
-
... ... @@ -1,73 +1,58 @@ 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,newcloudtemplatesfordockersingleand dockerdoublelaneareintroduced.Thesetemplates enable theabilityto cleanH2 databases fromtheportal.Nexttothis, itisnowpossibletoeditthetrigger"More than 100 messagesonqueueover10 minutes".Moroever,serveralcopytoclipboard buttons havebeenadded.Lastly, the runtime overviewhas beenimprovedwithrespecttocheckson theruntimeversion.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern. 7 7 8 - {{info}}Reminder! Asannouncedin ourprevious [[release blog>>Main.ReleaseInformation.ReleaseBlogs.216- Hack Heaven||target="blank"]], with thereleaseof the 11th of April:7 +== **Next generation improvements and bug fixes** == 9 9 10 - * TLSv1.0andTLSv1.1 will bedeprecated.11 - *Amajorversionofour[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]base image for allourclientsrunningon the[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]architecturewillbereleased.9 +//__Enhanced overview of the HTTP Statistics__// 10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 12 12 13 -For more information, please check out our [[release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]] from the previous release.{{/info}} 12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 14 14 15 -== **Cloud Template R12 Docker - Single Lane** == 16 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]]. 15 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 17 17 18 - == **CloudTemplate R14 Docker- Double Lane** ==19 -T hisrelease introducesa newnon-serviceaffectingcloud templateforall our customers runninginasingle-lanesetup.Thiscloud templateintroducestheability tocleanH2 databasesfromthe portal. The complete releasenotesonthecloudtemplatecan be found[[here>>doc:Main.ReleaseInformation.CloudTemplates.R14Docker - Double Lane.WebHome||target="blank"]].17 +//__Forced congestion control__// 18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 21 +//__Improved validation errors on the invalid configuration of HTTP outbound components__// 22 +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. 26 26 27 -//__Copy to clipboard buttons__// 28 -Copy to clipboard buttons have been added to various pages: 24 +//__Improved migration behavior__// 25 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 26 +A smoother migration of your JMS (and backup JMS) process. 27 +Shortening of names that otherwise would be too long, additional feedback given to the user. 28 +Feedback when the migration process is finished. 29 29 30 - * Deploy agent pop-up 31 - * Create - Flow designer: Properties 32 - * Deploy - Property releases: Property details 30 +//__Additional checks when deploying__// 31 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other. 33 33 34 - [[image:Main.Images.ReleaseBlog.WebHome@release-217-template-tango-copy-to-clipboard.png]]33 +== **Store Improvements** == 35 35 36 -//__Reset H2 database__// 37 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. 35 +== **Event Streaming - Certificate Management** == 38 38 39 -{{info}}Please note the following: 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. 44 - 45 -For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2||target="blank"]]{{/info}} 46 - 47 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 48 - 49 -== **Bug Fixes** == 50 -//__Runtime overview improvements__// 51 -The runtime overview has been improved regarding checks on the runtime version. 52 - 53 53 == **Fancy Forum Answers** == 54 54 55 55 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: 56 56 57 -* [[ XSDis onlypartiallyimportedintoeMagiz(xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]58 -* [[ TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]41 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 42 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 59 59 60 -== **Key Takeaways** ==44 +== **Key takeaways** == 61 61 62 -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:46 +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: 63 63 64 64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 65 * If you have feedback or ideas for us, talk to the Platypus 66 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 67 67 * Clear your browser cache (Ctrl + Shift + Del) 68 68 * Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development 70 70 * Start thinking about major, minor, and patch 55 +* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,11 +75,6 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -{{/info}} 79 -))) 80 - 81 -((( 82 -{{toc/}} 83 -))) 63 +~*~* Indicates a GEN3-only feature. 64 +{{/info}})))((({{toc/}}))){{/container}} 84 84 {{/container}} 85 -{{/container}}