Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version
To version 76.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +191 - Fifty Fifty
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,60 +2,106 @@
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 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.
5 +**Hi there, eMagiz developers!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
6 6  
7 -==**Flow Designer V3**==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
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.
9 +{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
11 +To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
15 15  
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.
13 +We offer alerting on five types.
22 22  
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.
15 +* Error message
16 +* Log message
17 +* Queue consumers
18 +* Messages in queue
19 +* Queue throughput
28 28  
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
21 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
37 37  
38 -
23 +These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
24 +
25 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
26 +
27 +Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
28 +
29 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
30 +
31 +== **Debugger ** ~*~* ~* ==
32 +
33 +{{warning}}Note that this functionality only works when the following criteria are met.
34 +* Your JMS server is running on the 3rd generation runtime
35 +* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 +* The beta image is activated
37 +* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
38 +
39 +As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
40 +
41 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
42 +
43 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
44 +
45 +Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
46 +
47 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
48 +
49 +{{info}}Note the following limitations when working with the debugger.
50 + * Your entire model needs to be migrated to the 3rd generation runtime
51 + * Only **one** flow **per** runtime can be debugged **per** environment
52 + * There is only **one** overview in which **all** debugged messages are shown
53 + * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54 + * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55 + ** After five minutes the debug functionality will be shutdown automatically under water.
56 + ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
57 +
58 +== **Volume mapping - Network Share** ==
59 +
60 +This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
61 +
62 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
63 +
64 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
65 +
39 39  == **Feedback items ** ==
40 40  
41 -We have also solved other feedback items besides the key updates around functionality.
68 +We have also solved other feedback items besides the flow designer's critical updates.
42 42  
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.
70 +//__Improved validation feedback on non-supported WSS4J interceptor __//
71 +We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 -
73 +//__Improve help text in flow testing on Java classes__//
74 +We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
48 48  
76 +//__Improved readibility of notification when trying to delete a runtime__//
77 +When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
78 +
79 +== **Bug fixes ** ==
80 +
81 +//__Keep selection when copying properties__//
82 +We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
83 +
84 +//__Check on security header improved for API Gateway__//
85 +We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
86 +
87 +//__Copy and paste default support objects__//
88 +With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
89 +
90 +//__Fix editability of properties when importing store items__//
91 +With this release, you can once again change property names upon importing a store item.
92 +
49 49  == **Fancy Forum Answers** ==
50 50  
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:
95 +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:
52 52  
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"]]
97 +* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98 +* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99 +* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
55 55  
56 56  == **Key takeaways** ==
57 57  
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:
104 +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:
59 59  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -66,12 +66,11 @@
66 66  * Start thinking about major, minor, and patch
67 67  * Upgrade to the latest build number
68 68  * Keep making great integrations
69 -* Check out the new documentation portal.
70 70  
71 71  Let's stay in touch and till next time!
72 72  
73 73  {{info}}
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]]
119 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 76  ~*~* Indicates a GEN3-only feature.
77 77  {{/info}})))((({{toc/}}))){{/container}}