Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 41.1
edited by Erik Bakker
on 2022/11/07 16:35
on 2022/11/07 16:35
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -18 7-Integration Sponsor1 +186 - Daemon Switch - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Content
-
... ... @@ -2,34 +2,40 @@ 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 re leasewewillreleaseseveral impactfulfeatures and enablersoourcommunity.AmongothersthenextphaseoftheMagizStore will becomepubliclyavailable.Thismeans thatyou cannow importdata models andtransformationon top ofsystem messagesin DesignandacceleratorsinCreate.Furthermore, we willlaunchanew Betafunctionalitythroughsome of ourclientsthatwill enableyoutorestoreyourflowto a previousversion.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- Nextphase** ==7 +== **New monitoring stack** == 8 8 9 -This release will introduce thenextphaseofthe Storetoourwholecommunity.Withthisnewfunctionality youcan now importdata modelmessages (i.e.CDM,API GatewayData model orEventStreamingdatamodel)andtransformations.Thiswayconnectingto standardized systemssuchasExactOnline,MicrosoftGraph,Salesforceandotherswillbecome eveneasier.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 moreinformationontheStorepleasecheckout this[[course>>doc:Main.eMagizAcademy.Microlearnings.Novice.eMagizStore.WebHome||target="blank"]].Asareminder you canfindalldocumentationonall availableStorecontentpublishedby eMagiz[[here>>doc:Main.eMagizStore.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 -== ** New eMagiz MendixConnector** ==18 +== **Academy improvements** == 16 16 17 - Withthis releaseweintroduce anewversionof theeMagiz Mendix Connector.Thisversion(6.0.0) willworkboth with thecurrent runtimearchitecturend the new runtime architecturemakingthe migrationfromthecurrentruntime architecture tothenewruntime architecture easier.Thenew versionoftheeMagiz MendixConnectorcanbefound intheMendixMarketplacedinthe eMagiz portal.20 +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. 18 18 19 - {{info}}Migratingtheruntime from the eMagiz portal works theamefor any otherruntime. The migration path to migratecanbe found [[here>>doc:Main.eMagiz Support.MigrationPaths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}22 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]] 20 20 21 -== **Flow version restore**~*==24 +== **Flow Designer Improvements** == 22 22 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. 26 +//__See last changed date and changed by on resource level__// 27 +This release will reinstate the ability to see who changed a resource last and when it was changed for the last time. You can find this information by double-clicking on a resource or viewing its details via the view button. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@18 7-release-blog--flow-version-restore.png]]29 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]] 26 26 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}} 31 +//__See on which other flows a resource is used__// 32 +This release will reinstate the ability to see whether a resource is used in other flows within your model or not. This will help to determine the impact of a specific change. 32 32 34 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]] 35 + 36 +//__Toggle option to see the generated resource by default__// 37 +Upon request, we have made the toggle for the generated resources in the new flow designer user-dependent. This means that you, as a user, can determine that the toggle should also be on. This means that the generated resources will be shown to you when opening any flow in eMagiz. When you switch the toggle off, this will mean that you will **not** see the generated resources by default. 38 + 33 33 == **Feedback items ** == 34 34 35 35 We have also solved other feedback items besides the flow designer's critical updates.