Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
Change comment: There is no comment for this version
To version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +185 - To determine
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -2,50 +2,60 @@
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 the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
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 -== **3rd generation improvements and bug fixes** ==
7 +==**Flow Designer V3**==
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed.
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 -{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
13 13  
14 -//__Removed certain dependencies between Deploy Architecture and Releases__//
15 -In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
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  
17 -//__Improved validation errors on invalid configuration of HTTP outbound components__//
18 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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.
19 19  
20 -//__Improved migration behavior__//
21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
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
22 22  
23 -//__Improved auto-healing when running in a hybrid situation__//
24 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
25 -
26 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
27 -To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
28 -
29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
30 -
38 +
31 31  == **Feedback items ** ==
32 32  
33 -//__Make sure the message format can be viewed without "Start editing"__//
34 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
41 +We have also solved other feedback items besides the key updates around functionality.
35 35  
36 -//__Various styling improvements in the flow testing functionality__//
37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
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.
38 38  
46 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 +
48 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 -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 +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:
42 42  
43 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
44 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||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"]]
45 45  
46 46  == **Key takeaways** ==
47 47  
48 -Thanks to all that helped build and those 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:
49 49  
50 50  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51 51  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -56,11 +56,12 @@
56 56  * Start thinking about major, minor, and patch
57 57  * Upgrade to the latest build number
58 58  * Keep making great integrations
69 +* Check out the new documentation portal.
59 59  
60 60  Let's stay in touch and till next time!
61 61  
62 62  {{info}}
63 -~* 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]]
64 64  
65 65  ~*~* Indicates a GEN3-only feature.
66 66  {{/info}})))((({{toc/}}))){{/container}}