Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
Change comment:
There is no comment for this version
To version 421.1
edited by CarlijnKokkeler
on 2024/03/25 12:28
on 2024/03/25 12:28
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 -2 04-Found It1 +217 - Template Tango - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,49 +1,62 @@ 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!** Wehave processedadditionalfeedback onthe releasepropertiesin thelastfewweeks.Ontop ofthat, wehaveimproved the error handlingandmanageability ofour newgeneration monitoringstack.6 +**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and docker double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version. 6 6 8 +== **Cloud Template R12 Docker - Single Lane** == 9 +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"]]. 10 + 11 +== **Cloud Template R14 Docker - Double Lane** == 12 +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.R14 Docker - Double Lane.WebHome||target="blank"]]. 13 + 7 7 == **Feedback Items** == 15 +//__Custom trigger__// 16 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger. 8 8 9 -//__Improved check on nested property placeholders__// 10 -To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing. 18 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 11 11 12 -//__ Removedoutdatedproperties whendeployingonthe new generationarchitecturestack__//13 - We have removedtwospecificoutdatedproperties from the configuration when deploying onthe new generationarchitecturestack.Theproperties in question were necessarybeforeinordertoconnect toaKafka clusterbut have become obsoleteonce you migrate.20 +//__Copy to clipboard buttons__// 21 +Copy to clipboard buttons have been added to various pages: 14 14 15 -{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}} 23 + * Deploy agent pop-up 24 + * Create - Flow designer: Properties 25 + * Deploy - Property releases: Property details 16 16 17 -//__Improved performance Manage Dashboards__// 18 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture. 27 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 19 19 20 -== **Bug Fixes** == 29 +//__Reset H2 database__// 30 +For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following: 21 21 22 -//__Errors with long stack traces or long message histories will now also show in eMagiz__// 23 -We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s). 32 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 33 +* 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. 34 +* For on-premise runtimes, only a reset of the runtime is needed. 24 24 25 -//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__// 26 -We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration. 36 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 27 27 38 +== **Bug Fixes** == 39 +//__Runtime overview improvements__// 40 +The runtime overview has been improved regarding checks on the runtime version. 41 + 28 28 == **Fancy Forum Answers** == 29 29 30 30 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: 31 31 32 -* [[XS LTExtensionGatewaywithJSONmessage>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]33 -* [[ eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]46 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 47 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 34 34 35 -== **Key takeaways** ==49 +== **Key Takeaways** == 36 36 37 37 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: 38 38 39 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 40 40 * If you have feedback or ideas for us, talk to the Platypus 41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 55 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 42 42 * Clear your browser cache (Ctrl + Shift + Del) 43 43 * Check out the release notes [here] 44 44 * Start thinking about how the license tracker can aid your development 45 45 * Start thinking about major, minor, and patch 46 -* Upgrade to the latest build number 47 47 * Keep making great integrations 48 48 49 49 Let's stay in touch and till next time! ... ... @@ -51,6 +51,11 @@ 51 51 {{info}} 52 52 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 54 -~*~* Indicates a next-generation-architecture only feature. 55 -{{/info}})))((({{toc/}}))){{/container}} 67 +{{/info}} 68 +))) 69 + 70 +((( 71 +{{toc/}} 72 +))) 56 56 {{/container}} 74 +{{/container}}