Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From 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
To version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
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 -18 7-IntegrationSponsor1 +189 - Private Eye - Content
-
... ... @@ -2,64 +2,71 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Thisreleasewillrelease severalimpactfulfeaturesandenablerstoourcommunity.Amongothers,thenextphase oftheeMagiz Storewillbecome publicly available.This meansthatyoucan now importdatamodelsand transformationon top ofsystemmessagesinDesignandacceleratorsinCreate. Furthermore,wewill launchanewBeta functionality through some of ourclients,enablingyoutorestoreyour flowtoa previousversion.5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -== **Store - Next phase** == 7 +== **Private Store** == 8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 8 8 9 - This releasewill introduce thenextphaseoftheStoreto our wholecommunity. Withthisnewfunctionality,youcanimportdata modelmessages (i.e., CDM, API Gateway Data model,or EventStreaming datamodel)andtransformations. Connectingtostandardized systemssuchas Exact Online,MicrosoftGraph, Salesforce,and otherswill becomeeven moreaccessible.10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 10 10 11 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--current-store-offering.png]]12 +== **3rd generation runtime bolstering** == 12 12 13 - {{info}}Formoreinformation on the Store pleasecheck out this[[course>>doc:Main.eMagizAcademy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]].As areminder,youcanfindalldocumentationonall availableStorecontentpublishedby eMagiz[[here>>doc:Main.eMagizStore.WebHome||target="blank"]].{{/info}}14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 14 14 15 -== **New eMagiz Mendix Connector** == 16 +//__SOAP and REST web services migration including splitting them__// 17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal. 16 16 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. 19 +//__Changing SSL settings for 3rd generation runtime models works__// 20 +As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime. 18 18 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}} 22 +//__Improved migration for JMS flows__// 23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 20 20 21 - ==**Flowversionrestore**~*==25 +{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 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. 27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 +As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 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 - 33 33 == **Feedback items ** == 34 34 35 35 We have also solved other feedback items besides the flow designer's critical updates. 36 36 37 -//__Improved helptextsKafkacomponent__//38 - The helptextsonvariousconfiguration optionsndthe general helptextonmultipleKafka components have been updatedtoclarifyhowtheyworkandhow you ought to configurethemtoachievethebestpossibleresultwhen sendingandreceiving messagestoandfrom topics withineMagiz.37 +//__Improved naming convention on Store related pages__// 38 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 39 39 40 -//__ Improved warning messagewhenMessageredeliverycannotbedequatelyexecuted__//41 - Wehaveimprovedthe warningyouget whenyoucannot retrievethemessages waitingtobe redelivered. Thishelpsclarifywhatisgoingwrongwhenauserseesthiswarning.40 +//__Press "Enter" to search on multiple pages__// 41 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 42 42 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. 43 +* Deploy → Deployment Plan 44 +* Deploy → Properties → History 45 +* Deploy → User Management → Roles 46 +* Manage → Error Messages → Error Messages 47 +* Manage → Error Messages → Flows with Error Messages 48 +* Manage → Error Messages → Exceptions of Error Messages 49 +* Manage → Log Entries 50 +* Manage → Alerts 51 +* Manage → Triggers 52 +* Manage → Tags – Cant find (only Gen2) 53 +* Manage → Notifications 54 +* Manage → Notification Settings 55 +* Manage → Data Usage → History 56 +* Manage → Code mappings → All tabs 45 45 46 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]58 +== **Bug fixes ** == 47 47 48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 60 +//__Loading problems of Deployment plan execution overview__// 61 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 49 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 - 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 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 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 68 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 69 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 63 63 64 64 == **Key takeaways** == 65 65