Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
on 2023/02/14 15:33
Change comment:
There is no comment for this version
To version 422.1
edited by CarlijnKokkeler
on 2024/03/25 14:39
on 2024/03/25 14:39
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 - 192 -Small Step1 +217 - Template Tango - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,70 +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!** In th elastcoupleofweeks,weworkedhardonbuildingseveralessential thingsthat willbereleasedlater thisQ.Ontopofthat,wefinishedadditionalfeatures for our3rdgenerationruntimethat giveyou chirurgicalprecisionwhendoingmaintenanceon amodel.Amongtheotherfeatures,wehavea neweventstreaminggraphandgeneralupdatesto ourplatform.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 7 -== **Start/Stop Flows** ~*~* == 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"]]. 8 8 9 -{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}} 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"]]. 10 10 11 -To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option. 14 +== **Feedback Items** == 15 +//__Dynamic trigger__// 16 +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. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@ 192-release-blog--start-stop-flows-context-menu.png]]18 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 14 14 15 -After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start. 20 +//__Copy to clipboard buttons__// 21 +Copy to clipboard buttons have been added to various pages: 16 16 17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 23 + * Deploy agent pop-up 24 + * Create - Flow designer: Properties 25 + * Deploy - Property releases: Property details 18 18 19 - {{info}}Only in "Start Editing"modecanyoustartand stopspecific flows{{/info}}27 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 20 20 21 -== **Manage overview Event Streaming** ~*~* == 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: 22 22 23 -To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data. 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 -[[image:Main.Images.Release Blog.WebHome@ 192-release-blog--event-streaming-overview-manage.png]]36 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 26 26 27 -== **Feedback items ** == 38 +== **Bug Fixes** == 39 +//__Runtime overview improvements__// 40 +The runtime overview has been improved regarding checks on the runtime version. 28 28 29 -We have also solved other feedback items besides the flow designer's critical updates. 30 - 31 -//__Topic configuration calculation__// 32 -With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics. 33 - 34 -//__Make preparation step in deployment plan visible__// 35 -For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan. 36 - 37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 38 - 39 -//__3rd generation runtime debugger feedback__// 40 -We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality. 41 - 42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__// 43 -As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows. 44 - 45 -//__User Management synchronization now happens in one step__// 46 -With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized. 47 - 48 48 == **Fancy Forum Answers** == 49 49 50 50 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: 51 51 52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]] 54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||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"]] 55 55 56 -== **Key takeaways** ==49 +== **Key Takeaways** == 57 57 58 -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:51 +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: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 -* 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. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 64 * Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development 66 66 * Start thinking about major, minor, and patch 67 -* Upgrade to the latest build number 68 68 * Keep making great integrations 69 69 70 70 Let's stay in touch and till next time! ... ... @@ -72,6 +72,11 @@ 72 72 {{info}} 73 73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 75 -~*~* Indicates a GEN3-only feature. 76 -{{/info}})))((({{toc/}}))){{/container}} 67 +{{/info}} 68 +))) 69 + 70 +((( 71 +{{toc/}} 72 +))) 77 77 {{/container}} 74 +{{/container}}