Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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 - 209-MaxVerstappen1 +185 - To determine - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.eMagiz - Content
-
... ... @@ -2,76 +2,64 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have done ... ..5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one. 6 6 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. 7 +==**Flow Designer V3**== 9 9 10 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 9 +The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider. 10 + 11 +=== **Improvements** === 12 +The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy. 11 11 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 14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 14 14 15 -== **Cloud Template R13 - Double Lane** == 16 +Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow. 17 + 18 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]] 19 + 20 +* **Alerts** 21 +In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location. 16 16 23 +* **Resources** 24 +In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these. 25 + 26 +* **Support objects** 27 +The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used. 17 17 18 -== **Feedback Items** == 29 +* **Properties** 30 +The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry. 31 + 32 +=== **User interaction changes** === 33 +There are some small changes to consider compared to the old flow designer. Please take a moment to read these: 34 + 35 +* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select 36 +* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier 19 19 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. 38 + 39 +== **Feedback items ** == 25 25 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. 41 +We have also solved other feedback items besides the key updates around functionality. 28 28 29 -//__ Queue explorermilliseconds__//30 - Thequeuebrowser nowdisplaysmillisecondsinstamps.43 +//__Set runtime field as first selected field on property level__// 44 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 31 31 32 - //__Cancelnd nextbuttonsorder__//33 - Theorderof 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.46 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 47 + 34 34 35 -//__Unused images__// 36 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 37 - 38 -//__Carwash logging__// 39 -A new logging feature enabling us to make better choices in encryption standards will be released. 40 - 41 -//__Static alerts queue consumers__// 42 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 43 - 44 -== **Bug Fixes** == 45 - 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. 48 - 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. 51 - 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. 54 - 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. 57 - 58 58 == **Fancy Forum Answers** == 59 59 60 -As always, this isa 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 +As always, a gentle reminder to all 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: 61 61 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"]] 53 +* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]] 54 +* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]] 66 66 67 - 68 68 == **Key takeaways** == 69 69 70 -Thanks to all whohelpedbuildandthose who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:58 +Thanks to all that help build, 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. 62 +* 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 ... ... @@ -78,12 +78,13 @@ 78 78 * Start thinking about major, minor, and patch 79 79 * Upgrade to the latest build number 80 80 * Keep making great integrations 69 +* Check out the new documentation portal. 81 81 82 82 Let's stay in touch and till next time! 83 83 84 84 {{info}} 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]]74 +~* 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 next-generation-architecture only feature.76 +~*~* Indicates a GEN3-only feature. 88 88 {{/info}})))((({{toc/}}))){{/container}} 89 89 {{/container}}