Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 138.1
edited by Erik Bakker
on 2023/08/01 14:28
on 2023/08/01 14:28
Change comment:
There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2022/11/08 08:19
on 2022/11/08 08:19
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 202-New Equilibrium1 +187 - Integration Sponsor - Content
-
... ... @@ -2,65 +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 thelast fewweeks, wehavecrossedourt's anddottedour i'son theleasepropertiesfunctionalitythat willimpacttheday-to-daylifeofeveryuserworkingwithintheplatform.Thefocus oftheleaseblogwillconsequentlyalsobeonthissubject. Onopofthat, wehaveseveralsmallerfeedbackitemsfrom ourhackathoneffortshat arenowreleasedtoyou.5 +**Hi there, eMagiz developers!** This release 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, enabling you to restore your flow to a previous version. 6 6 7 -== **Release Properties** == 8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are: 7 +== **Store - Next phase** == 9 9 10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 -* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration. 12 -* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers. 13 -* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment. 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. 14 14 15 - {{info}}Formoreformation, pleasecheckout thefollowingmicrolearnings:11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 16 16 17 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 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}} 20 20 21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 -{{/info}} 15 +== **New eMagiz Mendix Connector** == 23 23 24 -== ** Manage - Next generation graphs improvements ** == 25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out. 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. 26 26 27 - [[image:Main.Images.ReleaseBlog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]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}} 28 28 29 -== **Fe edbackItems** ==21 +== **Flow version restore** ~* == 30 30 31 -//__Improved editability when testing in eMagiz without Edit rights in Create__// 32 -Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description. 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. 33 33 34 -//__Improved auditability on Deploy Architecture__// 35 -To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP). 25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 36 36 37 -//__Test your own exported store content__// 38 -We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store. 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}} 39 39 40 - {{info}}Incasetheconcept of the store is new for you, pleasecheckout this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-magic-store.WebHome||target="blank"]]{{/info}}33 +== **Feedback items ** == 41 41 42 -//__Improved comparison of flows in the releases overview__// 43 -We have now made it possible to see the differences in the flow versions between the two releases for all three patterns. 35 +We have also solved other feedback items besides the flow designer's critical updates. 44 44 45 -== **Bug Fixes** == 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. 46 46 47 -//__Improved validationonXPathheaderenricher__//48 - Toavoid unexpectedbehaviorwhenfillingintheXPathheadernrichercomponent,wehavemprovedthevalidation on thiscomponent.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. 49 49 50 -//__ Cancel behavioron flowtestingpropertyoverviewfixed__//51 - Wehave ensured that whenyoupressCancel wheneditingapropertyneededinaflowtest,thepropertyplaceholder willnolonger disappearfromthe list.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. 52 52 53 -//__Cancel behavior on flow fragment level when exporting store content__// 54 -We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list. 46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 55 55 56 -//__Adding numbers on containers in Deploy Architecture__// 57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release. 48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 58 58 50 +== **Bug Fixes** == 51 + 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 + 59 59 == **Fancy Forum Answers** == 60 60 61 61 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: 62 62 63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||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"]] 64 64 65 65 == **Key takeaways** == 66 66