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 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +189 - Private Eye
Content
... ... @@ -2,102 +2,73 @@
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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **Dynamic Alerts** ~*~* ==
7 +== **Private Store** ==
8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
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}}
10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
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.
12 +== **3rd generation runtime bolstering** ==
12 12  
13 -We offer alerting on five types.
14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
16 +//__SOAP and REST web services migration, including splitting them__//
17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
19 +//__Changing SSL settings for 3rd generation runtime models works__//
20 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
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.
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
25 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
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.
27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
30 30  
31 -== **Debugger ** ~*~* ~* ==
33 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
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}}
36 +//__Added "Reset" functionality__//
37 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
38 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.
43 +//__Improved naming convention on Store related pages__//
44 +We have improved various display names using the merge functionality within our store offering.
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.
46 +//__Update security protocols for our internal architecture__//
47 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
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.
49 +//__Improved read-only description for "if exists" constructions in Transformations__//
50 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
78 78  
52 +
79 79  == **Bug fixes ** ==
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.
55 +//__Decent validation feedback when not filling in the property value__//
56 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
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.
58 +//__Incorrect resource locations__//
59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
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.
61 +//__Apply to environment in User Management performance improvement__//
62 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
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"]]
68 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
101 101  
102 102  == **Key takeaways** ==
103 103