Changes for page 210 - Deployment Delights
Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
on 2023/02/14 15:33
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 92-SmallStep1 +188 - Close Encounters - Content
-
... ... @@ -2,56 +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 lastcouple of weeks, we worked hard on building several essentialthingsthatwill beleasedlater this Q. Ontopofthat, weinishedadditionalfeatures for our 3rd generation runtimethatgiveyou chirurgical precision whendoingmaintenance on amodel.Amongtheotherfeatures,wehavea neweventstreaming graph andgeneralupdatestoour platform.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 -== **St art/StopFlows**~*~*==7 +== **Store - Next phase** == 8 8 9 - {{warning}}Note thatdependingonthealert,this functionalitywillonlyworkwhenyourJMSserverrunning on the3rdgenerationruntime{{/warning}}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 - To enhanceyour optionswhen running into problemsor whenmaintaining your solution in a Productionenvironment, we have added a new featureto our Deploy phasecalled "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview inDeploy. Onthe runtime level, you can open the context menu and select the "Start/Stop Flows" option.11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 12 12 13 - [[image:Main.Images.ReleaseBlog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]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 - Afterselectingtheoption, eMagizwill opena pop-up where you can stop andstart the startingpoint of each flow deployed onthat runtime. This effectis that the flow will processno new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.15 +== **New eMagiz Mendix Connector** == 16 16 17 - [[image:Main.Images.ReleaseBlog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.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. 18 18 19 -{{info}} Onlyin"StartEditing"modecanyoustart andstop specific flows{{/info}}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 -== ** ManageoverviewEventStreaming** ~*~*==21 +== **Flow version restore** ~* == 22 22 23 - To enhancetheobservabilityofyour eventstreaming solutionwhilerunningin the 3rd generationruntime architecture,we haveadded anewfeature to our Managephasecalled "Eventstreamingstatistics." Youcan accessthisfunctionalityviathe "Monitoring"menu in Manage.Then,youcan see metadata informationon allyourtopics by clickingonthe"Eventstreamingstatistics"overview. Amongothers, you cansee whether dataisconsumed,onwhichtopic much data isproduced,andwhether consumers arelagging inconsuming data.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 -[[image:Main.Images.Release Blog.WebHome@1 92-release-blog--event-streaming-overview-manage.png]]25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.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}} 32 + 27 27 == **Feedback items ** == 28 28 29 29 We have also solved other feedback items besides the flow designer's critical updates. 30 30 31 -//__ Topicconfigurationcalculation__//32 - Withthis release,wehave simplifiedtheconfiguration of settingson thetopic level to enforcecertainbestpracticeswithintheportalandsimultaneouslymakeit easiertoconfigure topics.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. 33 33 34 -//__ Makepreparation stepin deploymentplanvisible__//35 - Fordeploymentonthe3rd generationruntimetowork,theportal needsomepreparationwork.Wehavenow madethisstepexplicitandpartofthedeploymentplan.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. 36 36 37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 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. 38 38 39 -//__3rd generation runtime debugger feedback__// 40 -We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality. 46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 41 41 42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__// 43 -As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows. 48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 44 44 45 -//__User Management synchronization now happens in one step__// 46 -With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized. 50 +== **Bug Fixes** == 47 47 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 + 48 48 == **Fancy Forum Answers** == 49 49 50 50 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: 51 51 52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]] 54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||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"]] 55 55 56 56 == **Key takeaways** == 57 57