Skip to Content

Changes for page 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
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 81.1
edited by Erik Bakker
on 2023/02/13 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +192 - Small Step
Content
... ... @@ -2,14 +2,22 @@
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!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger functionality.
6 6  
7 -== **Dynamic Alerts** ~*~* ==
7 +== **Start/Stop Flows** ~*~* ==
8 8  
9 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 -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 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12 12  
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
14 +
15 +
16 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
17 +
18 +
19 + 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.
20 +
13 13  We offer alerting on five types.
14 14  
15 15  * Error message
... ... @@ -33,7 +33,6 @@
33 33  {{warning}}Note that this functionality only works when the following criteria are met.
34 34  * Your JMS server is running on the 3rd generation runtime
35 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 37  * A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
38 38  
39 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.
... ... @@ -67,6 +67,9 @@
67 67  
68 68  We have also solved other feedback items besides the flow designer's critical updates.
69 69  
77 +//__Show status on machine level under Deploy Architecture__//
78 +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.
79 +
70 70  //__Improved validation feedback on non-supported WSS4J interceptor __//
71 71  We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
72 72  
... ... @@ -76,6 +76,27 @@
76 76  //__Improved readibility of notification when trying to delete a runtime__//
77 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 78  
89 +//__Improved sorting of missing properties overview__//
90 +We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
91 +
92 +//__Improved notification when error message cannot be found__//
93 +We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
94 +
95 +//__Additional lifecycle management overview__//
96 +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.
97 +
98 +//__Improved feedback when memory settings are negative__//
99 +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.
100 +
101 +//__Auto upgrade for a cloud template default to "ON"__//
102 +For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
103 +
104 +//__Removed an irrelevant refresh button on a flow designer component__//
105 +We have removed an irrelevant refresh button on the standard filter component.
106 +
107 +//__Notification list shows all notifications on default__//
108 +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.
109 +
79 79  == **Bug fixes ** ==
80 80  
81 81  //__Keep selection when copying properties__//
... ... @@ -84,20 +84,31 @@
84 84  //__Check on security header improved for API Gateway__//
85 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 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.
118 +//__Don't show systems with only "external" flows in Design__//
119 +We fixed a bug that caused systems to appear in Design in cases where there should be none.
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.
121 +//__Fix styling of mendix login in some occurences__//
122 +When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
92 92  
124 +//__Change timing of wake-up of cloud slots on Friday__//
125 +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.
126 +
127 +//__Fixed a typo in the Topic statistics overview__//
128 +We fixed a typo in the topic statistics overview.
129 +
130 +//__Fixed a typo in the HTTP statistics overview__//
131 +We fixed a typo in the HTTP statistics overview.
132 +
133 +//__Activatation of release history when executing a deployment__//
134 +We ensured that the release history is activated when executing a deployment.
135 +
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"]]
140 +* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
141 +* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
142 +* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
101 101  
102 102  == **Key takeaways** ==
103 103