Skip to Content

Changes for page 186 - Daemon Switch

Last modified by Carlijn Kokkeler on 2024/04/18 13:22
From version 30.1
edited by Erik Bakker
on 2022/10/24 11:04
Change comment: There is no comment for this version
To version 37.1
edited by Erik Bakker
on 2023/10/03 10:30
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,6 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 5  **Hi there, eMagiz developers!** We have hit the ground running this quarter by focusing on more prominent features and spending a substantial chunk of time focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to the first set of models. So let us dive into all we have to offer this time!
... ... @@ -9,11 +9,13 @@
9 9  This release will introduce a new monitoring stack available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack, we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of these changes, please check out the following microlearnings.
10 10  
11 11  * [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
12 -* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]]
13 -* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]]
14 -* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]]
13 +* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]
14 +* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3||target="blank"]]
15 +* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-http-statistics.WebHome||target="blank"]]
15 15  
16 -{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}}
17 +{{info}}
18 +Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities
19 +{{/info}}
17 17  
18 18  == **Academy improvements** ==
19 19  
... ... @@ -78,7 +78,9 @@
78 78  //__Improved update functionality of Swagger file when changing data model__//
79 79  Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly.
80 80  
81 -{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}}
84 +{{info}}
85 +Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s)
86 +{{/info}}
82 82  
83 83  //__"Disapprove and go to environment"__//
84 84  Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
... ... @@ -89,6 +89,8 @@
89 89  //__Add Topic Storage information to License Tracker__//
90 90  On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz.
91 91  
97 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
98 +
92 92  //__Add Compatibility check when importing store items__//
93 93  We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening.
94 94  
... ... @@ -98,6 +98,9 @@
98 98  //__Improve rendering of validation definition when using multiple namespaces__//
99 99  With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end.
100 100  
108 +//__Improved help texts on next-generation runtime functionality across the portal__//
109 +With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime.
110 +
101 101  == **Bug Fixes** ==
102 102  
103 103  //__Provide correct feedback when a flow is transferred to Deploy for the first time__//
... ... @@ -121,7 +121,7 @@
121 121  //__Prevent users without view rights from seeing a weird screen in those phases__//
122 122  With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently.
123 123  
124 -//__name of starting point of the flow test is incorrect__//
134 +//__Name of starting point of the flow test is incorrect__//
125 125  With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct.
126 126  
127 127  //__Audit Trail on User Management could break__//
... ... @@ -137,11 +137,9 @@
137 137  
138 138  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:
139 139  
140 -* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
141 -* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
142 -* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
150 +* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
151 +* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
143 143  
144 -
145 145  == **Key takeaways** ==
146 146  
147 147  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:
... ... @@ -162,5 +162,11 @@
162 162  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
163 163  
164 164  ~*~* Indicates a GEN3-only feature.
165 -{{/info}})))((({{toc/}}))){{/container}}
173 +{{/info}}
174 +)))
175 +
176 +(((
177 +{{toc/}}
178 +)))
166 166  {{/container}}
180 +{{/container}}