Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
on 2023/08/01 13:48
Change comment:
There is no comment for this version
To version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
on 2023/11/21 11:09
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 -20 2-NewEquilibrium1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,76 +2,76 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In thelast few weeks, wehavecrossedur t's and dottedour i's on the release properties functionality that will impact the day to day life of every user working within the platform.The focus of the release blog will consequently also be on this subject.On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.5 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 -== ** ReleaseProperties** ==8 - Asofthis release,we will introduceanewway of handlingproperties forall ourlients. Thereare severalkeychanges comparedto thecurrent wayofmanagingyourproperties.7 +== **Next Generation Architecture Default** == 8 +With this release, the next generation architecture will become the default. New models will use this generation as default. 9 9 10 - {{info}}Formoreformation pleasecheckout thefollowingmicrolearnings:10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 11 11 12 -* 13 -* 14 -* 12 +== **Cloud Template R11 - Single Lane** == 13 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here 15 15 16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 17 -{{/info}} 15 +== **Cloud Template R13 - Double Lane** == 18 18 19 -== ** Deploy Architecture - Apply To Environment improvements ** == 20 -As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button. 21 21 22 - [[image:Main.Images.ReleaseBlog.WebHome@201-release-blog--apply-to-environment-example.png]]18 +== **Feedback Items** == 23 23 24 -== ** Breadcrumb navigation in eMagiz ** == 25 -This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel. 20 +//__Unused properties overview__// 21 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 22 +* Not used by any runtime that is in the Create phase release. 23 +* Not required by a flow that is in the Create phase release. 24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 26 +//__Send build requests asynchronously__// 27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 28 28 29 -== **Feedback Items** == 29 +//__Queue explorer milliseconds__// 30 +The queue browser now displays milliseconds in the timestamps. 30 30 31 -//__ Improved layout ofcatalogpageinDesign__//32 - Wehaveimprovedthelayout of theAPI CatalogoverviewinDesignforour API Gatewayusers.Among others,we haveintroducedascrollbartogeta better overviewofseveraloperations.32 +//__Cancel and next buttons order__// 33 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 33 33 34 -//__ Improved layout of "Edit integration" pop-up for API Gatewayintegrations__//35 - Currently, thefull path of your backend systemwill behownwhenopeningthe"Editintegration"pop-up on your API Gatewayintegration.35 +//__Unused images__// 36 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 36 36 37 -//__ Additionalhelptextson Design Architecture__//38 - Wehaveimproved the help textsinDesignArchitectureconcerning theEventStreamingtopicstorageoverview.38 +//__Carwash logging__// 39 +A new logging feature enabling us to make better choices in encryption standards will be released. 39 39 40 -//__ Improved AuditTrailonseveralplaces__//41 - In severalplacesinthe portal,wehaveimprovedtheaudittrailtospecifybetterwhochangedwhatatwhichpointintime.41 +//__Static alerts queue consumers__// 42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 42 42 43 -//__Removed the erroneous alert on message mapping when having a passthrough API__// 44 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 45 - 46 46 == **Bug Fixes** == 47 47 48 -//__ Avoid clickingon other componentswhiledeleting another__//49 - Toavoidunexpectedbehavior,wenowensure thatnothing canbeselectedonceyouethe"deletion"pop-up whenyou want toremovesomethingintheflowdesigner.46 +//__Images rebuild__// 47 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped. 50 50 51 -//__ Improved validationfeedbackin migrating to the next-generationarchitecture__//52 - We have improved thevalidationfeedback whenmigratingtothenext-generationarchitecture.49 +//__Flow Designer connection line__// 50 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 53 53 54 -//__ Make surethatusercredentials can beviewedwith view rights__//55 - Thisreleasemakessurethattheusercredentials inDeploycanbe consideredwithviewrightsandnotonlywhenhavingit rights.52 +//__Portal for migrated models__// 53 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 56 56 57 -//__ Refresh behaviorwithinthedeploymentplanis fixed__//58 - This release changestherefreshbehaviorwithin thedeploymentplantoshow,oncemore, the"to beinstalled" flowsbeforetheuserpressesExecute.55 +//__Error channel inbounds__// 56 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 59 59 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 64 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 65 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 66 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 67 67 67 + 68 68 == **Key takeaways** == 69 69 70 -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:70 +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: 71 71 72 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 * If you have feedback or ideas for us, talk to the Platypus 74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 75 75 * Clear your browser cache (Ctrl + Shift + Del) 76 76 * Check out the release notes [here] 77 77 * Start thinking about how the license tracker can aid your development ... ... @@ -84,6 +84,6 @@ 84 84 {{info}} 85 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 87 -~*~* Indicates a GEN3-only feature.87 +~*~* Indicates a next-generation-architecture only feature. 88 88 {{/info}})))((({{toc/}}))){{/container}} 89 89 {{/container}}