Skip to Content

Changes for page 190 - Fast Forward

Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 39.1
edited by Erik Bakker
on 2022/11/07 16:15
Change comment: There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2022/10/24 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +186 - Daemon Switch
Content
... ... @@ -2,32 +2,19 @@
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!** 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!
6 6  
7 -== **Store - Next phase** ==
7 +== **New monitoring stack** ==
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 +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 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
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"]]
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}}
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}}
14 14  
15 -== **eMagiz Mendix Connector - 3rd generation runtime** ==
16 -
17 -
18 -
19 -== **Flow version restore** ~* ==
20 -
21 -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.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
24 -
25 -{{warning}}Note, that the following restrictions apply when restoring to a previous version:
26 - * Changes made on definition and transformation level are **not** restored
27 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
28 - * 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
29 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
30 -
31 31  == **Academy improvements** ==
32 32  
33 33  On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning.
... ... @@ -102,8 +102,6 @@
102 102  //__Add Topic Storage information to License Tracker__//
103 103  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.
104 104  
105 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
106 -
107 107  //__Add Compatibility check when importing store items__//
108 108  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.
109 109  
... ... @@ -113,9 +113,6 @@
113 113  //__Improve rendering of validation definition when using multiple namespaces__//
114 114  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.
115 115  
116 -//__Improved help texts on next-generation runtime functionality across the portal__//
117 -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.
118 -
119 119  == **Bug Fixes** ==
120 120  
121 121  //__Provide correct feedback when a flow is transferred to Deploy for the first time__//
... ... @@ -139,7 +139,7 @@
139 139  //__Prevent users without view rights from seeing a weird screen in those phases__//
140 140  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.
141 141  
142 -//__Name of starting point of the flow test is incorrect__//
124 +//__name of starting point of the flow test is incorrect__//
143 143  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.
144 144  
145 145  //__Audit Trail on User Management could break__//
... ... @@ -155,9 +155,11 @@
155 155  
156 156  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:
157 157  
158 -* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
159 -* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||target="blank"]]
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"]]
160 160  
144 +
161 161  == **Key takeaways** ==
162 162  
163 163  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: