Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
Change comment: There is no comment for this version
To version 77.1
edited by Erik Bakker
on 2023/01/31 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +191 - Fifty Fifty
Content
... ... @@ -2,60 +2,137 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.
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 -== **Store - Next phase** ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
9 -This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
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}}
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.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.
12 12  
13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
13 +We offer alerting on five types.
14 14  
15 -== **New eMagiz Mendix Connector** ==
15 +* Error message
16 +* Log message
17 +* Queue consumers
18 +* Messages in queue
19 +* Queue throughput
16 16  
17 -With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
21 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
18 18  
19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
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.
20 20  
21 -== **Flow version restore** ~* ==
25 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
22 22  
23 -On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect.
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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
29 +[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
26 26  
27 -{{warning}}Note, that the following restrictions apply when restoring to a previous version:
28 - * Changes made on definition and transformation level are **not** restored
29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
31 +== **Debugger ** ~*~* ~* ==
32 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 +
33 33  == **Feedback items ** ==
34 34  
35 35  We have also solved other feedback items besides the flow designer's critical updates.
36 36  
37 -//__Improved help texts Kafka component__//
38 -TBA
70 +//__Show status on machine level under Deploy Architecture__//
71 +With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
39 39  
40 -//__Improved warning message when Message redelivery cannot be properly executed__//
41 -TBA
73 +//__Improved validation feedback on non-supported WSS4J interceptor __//
74 +We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -TBA
76 +//__Improve help text in flow testing on Java classes__//
77 +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.
45 45  
46 -== **Bug Fixes** ==
79 +//__Improved readibility of notification when trying to delete a runtime__//
80 +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.
47 47  
48 -//__Update Swagger File when changing order of entities in gateway message__//
49 -TBA
82 +//__Improved sorting of missing properties overview__//
83 +We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
50 50  
85 +//__Improved notification when error message cannot be found__//
86 +We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
87 +
88 +//__Additional lifecycle management overview__//
89 +We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
90 +
91 +//__Improved feedback when memory settings are negative__//
92 +We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
93 +
94 +//__Auto upgrade for a cloud template default to "ON"__//
95 +For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
96 +
97 +//__Removed an irrelevant refresh button on a flow designer component__//
98 +We have removed an irrelevant refresh button on the standard filter component.
99 +
100 +//__Notification list shows all notifications on default__//
101 +When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
102 +
103 +== **Bug fixes ** ==
104 +
105 +//__Keep selection when copying properties__//
106 +We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
107 +
108 +//__Check on security header improved for API Gateway__//
109 +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.
110 +
111 +//__Don't show systems with only "external" flows in Design__//
112 +We fixed a bug that caused systems to appear in Design in cases where there should be none.
113 +
114 +//__Fix styling of mendix login in some occurences__//
115 +When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
116 +
117 +//__Change timing of wake-up of cloud slots on Friday__//
118 +To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
119 +
120 +//__Fixed a typo in the Topic statistics overview__//
121 +We fixed a typo in the topic statistics overview.
122 +
123 +//__Fixed a typo in the HTTP statistics overview__//
124 +We fixed a typo in the HTTP statistics overview.
125 +
126 +//__Activatation of release history when executing a deployment__//
127 +We ensured that the release history is activated when executing a deployment.
128 +
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
56 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
57 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
58 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
133 +* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
134 +* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
135 +* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
59 59  
60 60  == **Key takeaways** ==
61 61