Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
on 2022/11/21 12:31
Change comment:
There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2022/11/21 12:00
on 2022/11/21 12:00
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,31 +2,29 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 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 lerfixes and beta features will be released to the community.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 -== ** 3rd generationruntimebolstering** ==7 +== **Store - Next phase** == 8 8 9 -This release will introduce various improvementsforour 3rd generationruntime.Belowyou willfindthemost noteworthy improvementswemade tothe3rdgenerationruntimeand the interactionwithit.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. 10 10 11 - //__Migration of JMSbackup configuration improved__//11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 12 12 13 - //__Prechecks onUpgrade optionmade availablefor3rd generationruntime__//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}} 14 14 15 - //__Autogeneratedexitscan beeployedatonce__//15 +== **New eMagiz Mendix Connector** == 16 16 17 - //__Codemappingfunctionalityavailable on3rdgeneration runtime__//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. 18 18 19 - //__Improvedtheperformanceofploying or activatingalease__//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}} 20 20 21 - //__Failingruntimeswon'tberestartedindefinetlyanymore__//21 +== **Flow version restore** ~* == 22 22 23 - ==**ExportableReleaseAudit**~*==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. 24 24 25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 26 - 27 27 [[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 28 28 29 -{{warning}}Note that the following restrictions apply when e xportinganauditdocument:27 +{{warning}}Note that the following restrictions apply when restoring to a previous version: 30 30 * Changes made on definition and transformation level are **not** restored 31 31 * You will **not** be able to restore to any flow version that was created before October 17th, 2022 32 32 * 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 ... ... @@ -36,30 +36,24 @@ 36 36 37 37 We have also solved other feedback items besides the flow designer's critical updates. 38 38 39 -//__ DataSinkRefactor__//40 - We havemademeinfrastructuralchangestohowdata sink messagesarestoredandcan beretrievedfromtheportal.Shouldtherebe changesneededonyourndwewillcontactyourseperately.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. 41 41 42 -//__Improved namingconventiononStore relatedpages__//43 -We have improved variousdisplay namestoensure thatitsclearfromthenamingthat storecontentcanbeimplementedin all integrationpatterns.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. 44 44 45 -//__ Press "Enter"to searchonmultiplepages__//46 - InourDaemonSwitchreleasewe addedfunctionalitythat allowedyou to press **Enter** to search on thepropertyoverviewpage. With this releasewehave addedthisfunctionalitytomanymore pagesacrosstheportal. Thecompletelist isasfollows43 +//__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. 47 47 48 -* Deploy → Deployment Plan 49 -* Deploy → Properties → History 50 -* Deploy → User Management → Roles 51 -* Manage → Error Messages → Error Messages 52 -* Manage → Error Messages → Flows with Error Messages 53 -* Manage → Error Messages → Exceptions of Error Messages 54 -* Manage → Log Entries 55 -* Manage → Alerts 56 -* Manage → Triggers 57 -* Manage → Tags – Cant find (only Gen2) 58 -* Manage → Notifications 59 -* Manage → Notification Settings 60 -* Manage → Data Usage → History 61 -* Manage → Code mappings → All tabs 46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 62 62 48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 49 + 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 + 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: