Changes for page 217 - Template Tango
Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 139.1
edited by Erik Bakker
on 2023/08/01 14:28
on 2023/08/01 14:28
Change comment:
There is no comment for this version
To version 432.1
edited by Erik Bakker
on 2024/03/26 14:09
on 2024/03/26 14:09
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 -2 02-New Equilibrium1 +217 - Template Tango - Content
-
... ... @@ -1,79 +1,73 @@ 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 elastfewweeks,wehavecrossedourt's and dottedour i's onthereleasepropertiesfunctionalitythatwillimpact the day-to-day lifeof everyuserworkingwithintheplatform.The focus ofthe releaseblog will consequentlyalsobeonthis subject.On topof that, wehave several smallerfeedbackitemsfrom our hackathoneffortsthatarenowreleasedtoyou.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 -== **Release Properties** == 8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are: 8 +{{info}}Reminder! As announced in our previous [[release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]], with the release of the 11th of April: 9 9 10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 -* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration. 12 -* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers. 13 -* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment. 10 +* TLSv1.0 and TLSv1.1 will be deprecated. 11 +* A major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture will be released. 14 14 15 - {{info}}For more information, please check outthe following microlearnings: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}} 16 16 17 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 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"]]. 20 20 21 - Shouldyouhave any questions in advance,pleasegetin touchwithus at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].22 - {{/info}}18 +== **Cloud Template R14 Docker - Double Lane** == 19 +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"]]. 23 23 24 -== ** Manage - Next generation graphs improvements ** == 25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out. 26 - 27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 28 - 29 29 == **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. 30 30 31 -//__Improved editability when testing in eMagiz without Edit rights in Create__// 32 -Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description. 25 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 33 33 34 -//__ Improved auditability onDeploy Architecture__//35 - Toimprovetheaudibility of Deploy Architecture, we now alsolog whensomeonewith Adminrights changesspecific functionson thislevel (i.e., Fixed IP).27 +//__Copy to clipboard buttons__// 28 +Copy to clipboard buttons have been added to various pages: 36 36 37 -//__Test your own exported store content__// 38 -We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store. 30 + * Deploy agent pop-up 31 + * Create - Flow designer: Properties 32 + * Deploy - Property releases: Property details 39 39 40 - {{info}}In case the concept of the store is new for you, please check out this[[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}34 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 41 41 42 -//__ Improved comparisonofflows inthe releases overview__//43 - Wehave nowmadeitpossibleto seethedifferencesintheflowversionsbetweenthetworeleasesforallthreepatterns.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. 44 44 45 - == **Bug Fixes**==39 +{{info}}Please note the following: 46 46 47 -//__Improved validation on XPath header enricher__// 48 -To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component. 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. 49 49 50 -//__Cancel behavior on flow testing property overview fixed__// 51 -We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list. 45 +For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}} 52 52 53 -//__Cancel behavior on flow fragment level when exporting store content__// 54 -We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list. 47 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 55 55 56 -//__Adding numbers on containers in Deploy Architecture__// 57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release. 49 +== **Bug Fixes** == 50 +//__Runtime overview improvements__// 51 +The runtime overview has been improved regarding checks on the runtime version. 58 58 59 59 == **Fancy Forum Answers** == 60 60 61 61 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: 62 62 63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 57 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 58 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 64 64 65 -== **Key takeaways** ==60 +== **Key Takeaways** == 66 66 67 -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:62 +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: 68 68 69 69 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 * If you have feedback or ideas for us, talk to the Platypus 71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 72 * Clear your browser cache (Ctrl + Shift + Del) 73 73 * Check out the release notes [here] 74 74 * Start thinking about how the license tracker can aid your development 75 75 * Start thinking about major, minor, and patch 76 -* Upgrade to the latest build number 77 77 * Keep making great integrations 78 78 79 79 Let's stay in touch and till next time! ... ... @@ -81,6 +81,11 @@ 81 81 {{info}} 82 82 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 83 83 84 -~*~* Indicates a GEN3-only feature. 85 -{{/info}})))((({{toc/}}))){{/container}} 78 +{{/info}} 79 +))) 80 + 81 +((( 82 +{{toc/}} 83 +))) 86 86 {{/container}} 85 +{{/container}}