Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
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 -199 - Home Improvements
1 +185 - To determine
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -2,48 +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 various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
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 improvements and bug fixes** ==
7 +==**Flow Designer V3**==
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
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 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
14 14  
15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
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 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
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  
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
20 20  
21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 -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.
38 +
39 +== **Feedback items ** ==
23 23  
24 -//__Improved migration behavior__//
25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 -A smoother migration of your JMS (and backup JMS) process.
27 -Shortening of names that otherwise would be too long, additional feedback given to the user.
28 -Feedback when the migration process is finished.
41 +We have also solved other feedback items besides the key updates around functionality.
29 29  
30 -//__Additional checks when deploying__//
31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
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.
32 32  
33 -== **Store Improvements** ==
46 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 +
34 34  
35 -== **Event Streaming - Certificate Management** ==
36 -
37 37  == **Fancy Forum Answers** ==
38 38  
39 -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:
40 40  
41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||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"]]
43 43  
44 44  == **Key takeaways** ==
45 45  
46 -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:
47 47  
48 48  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49 49  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -54,11 +54,12 @@
54 54  * Start thinking about major, minor, and patch
55 55  * Upgrade to the latest build number
56 56  * Keep making great integrations
69 +* Check out the new documentation portal.
57 57  
58 58  Let's stay in touch and till next time!
59 59  
60 60  {{info}}
61 -~* 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]]
62 62  
63 63  ~*~* Indicates a GEN3-only feature.
64 64  {{/info}})))((({{toc/}}))){{/container}}