Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 75.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2022/11/08 08:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +187 - Integration Sponsor
Content
... ... @@ -2,102 +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!** 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.
5 +**Hi there, eMagiz developers!** This release 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, enabling you to restore your flow to a previous version.
6 6  
7 -== **Dynamic Alerts** ~*~* ==
7 +== **Store - Next phase** ==
8 8  
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}}
9 +This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
10 10  
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.
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
12 12  
13 -We offer alerting on five types.
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}}
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
15 +== **New eMagiz Mendix Connector** ==
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
17 +This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
22 22  
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.
19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
21 +== **Flow version restore** ~* ==
26 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.
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.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
30 30  
31 -== **Debugger ** ~*~* ~* ==
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}}
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 -
66 66  == **Feedback items ** ==
67 67  
68 68  We have also solved other feedback items besides the flow designer's critical updates.
69 69  
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.
37 +//__Improved help texts Kafka component__//
38 +The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
72 72  
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.
40 +//__Improved warning message when Message redelivery cannot be adequately executed__//
41 +We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
75 75  
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.
43 +//__See Flow Designer errors on the Create overview__//
44 +To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
78 78  
79 -== **Bug fixes ** ==
46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
80 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.
48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
83 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.
50 +== **Bug Fixes** ==
86 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.
52 +//__Update Swagger File when changing the order of entities in gateway message__//
53 +In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
89 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 -
93 93  == **Fancy Forum Answers** ==
94 94  
95 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:
96 96  
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"]]
59 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
101 101  
102 102  == **Key takeaways** ==
103 103