Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 334.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
Change comment: There is no comment for this version
To version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,55 +1,74 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
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.
7 7  
8 -== **Feedback Items** ==
7 +== **Store - Next phase** ==
9 9  
10 -//__Failover setup__//
11 -New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||target="blank"]]
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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
14 14  
15 -//__External recipients emailaddress__//
16 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
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}}
17 17  
18 -//__Broker queue metrics dashboards__//
19 -It is now possible to select the MQTT broker in the queue metrics dashboards.
15 +== **New eMagiz Mendix Connector** ==
20 20  
21 -//__Runtime image version__//
22 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
17 +With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
23 23  
19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
24 24  
25 -== **Bug Fixes** ==
21 +== **Flow version restore** ~* ==
26 26  
27 -//__Message throughput__//
28 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
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.
29 29  
30 -//__Cloud template upgrade incorrect rollback__//
31 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
32 32  
33 -//__Next generation block__//
34 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
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}}
35 35  
33 +== **Feedback items ** ==
34 +
35 +We have also solved other feedback items besides the flow designer's critical updates.
36 +
37 +//__Improved help texts Kafka component__//
38 +TBA
39 +
40 +//__Improved warning message when Message redelivery cannot be properly executed__//
41 +TBA
42 +
43 +//__See Flow Designer errors on the Create overview__//
44 +TBA
45 +
46 +== **Bug Fixes** ==
47 +
48 +//__Update Swagger File when changing order of entities in gateway message__//
49 +TBA
50 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
55 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
56 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
57 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
58 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
41 41  
42 42  == **Key takeaways** ==
43 43  
44 -Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
62 +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:
45 45  
46 46  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 50  * Check out the release notes [here]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
71 +* Upgrade to the latest build number
53 53  * Keep making great integrations
54 54  
55 55  Let's stay in touch and till next time!
... ... @@ -57,11 +57,6 @@
57 57  {{info}}
58 58  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  
60 -{{/info}}
61 -)))
62 -
63 -(((
64 -{{toc/}}
65 -)))
79 +~*~* Indicates a GEN3-only feature.
80 +{{/info}})))((({{toc/}}))){{/container}}
66 66  {{/container}}
67 -{{/container}}