Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2022/11/21 12:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +188 - Close Encounters
Content
... ... @@ -2,68 +2,64 @@
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 few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
7 +== **Store - Next phase** ==
9 9  
10 -{{info}}For more information please check out the following microlearnings:
9 +This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
11 11  
12 -*
13 -*
14 -*
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
15 15  
16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 -{{/info}}
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}}
18 18  
19 -== ** Deploy Architecture - Apply To Environment improvements ** ==
20 -As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
15 +== **New eMagiz Mendix Connector** ==
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
17 +This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
23 23  
24 -== ** Breadcrumb navigation in eMagiz ** ==
25 -This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
21 +== **Flow version restore** ~* ==
28 28  
29 -== **Feedback Items** ==
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.
30 30  
31 -//__Improved layout of catalog page in Design__//
32 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
33 33  
34 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35 -Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
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}}
36 36  
37 -//__Additional help texts on Design Architecture__//
38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
33 +== **Feedback items ** ==
39 39  
40 -//__Improved Audit Trail on several places__//
41 -In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
35 +We have also solved other feedback items besides the flow designer's critical updates.
42 42  
43 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
44 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
37 +//__Improved help texts Kafka component__//
38 +The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
45 45  
46 -== **Bug Fixes** ==
40 +//__Improved warning message when Message redelivery cannot be adequately executed__//
41 +We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
47 47  
48 -//__Avoid clicking on other components while deleting another__//
49 -To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
43 +//__See Flow Designer errors on the Create overview__//
44 +To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
50 50  
51 -//__Improved validation feedback in migrating to the next-generation architecture__//
52 -We have improved the validation feedback when migrating to the next-generation architecture.
46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
53 53  
54 -//__Make sure that user credentials can be viewed with view rights__//
55 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
56 56  
57 -//__Refresh behavior within the deployment plan is fixed__//
58 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
50 +== **Bug Fixes** ==
59 59  
52 +//__Update Swagger File when changing the order of entities in gateway message__//
53 +In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
54 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
59 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
67 67  
68 68  == **Key takeaways** ==
69 69