Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From 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
To version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
on 2023/02/14 14:42
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 89 -PrivateEye1 +192 - Small Step - Content
-
... ... @@ -2,71 +2,56 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Ourrelease ofthePrivatestorefunctionalitycharacterizesthisrelease.Thisfunctionalityallowssomeusers to export content toaprivate storethatis only accessiblewithinthecompany and couldbepublished tothe publicstoreof eMagiz. On top of that,weresolvedsomeof the limitations onthe3rd generation runtime.Furthermore,someminorfixesandbeta features willbereleasedto thecommunity.5 +**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general. 6 6 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). 7 +== **Start/Stop Flows** ~*~* == 9 9 10 -{{warning}} Otherusers cansee thestorecontentbutarenotabletoimportthestorecontent.Theywillbenotifiedto themwhenthey trytodo so.{{/warning}}9 +{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}} 11 11 12 - ==**3rdgeneration runtimebolstering**==11 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows". 13 13 14 - This releasewill introduce various improvementsfor our 3rd generation runtime.Below you will find themost noteworthyenhancementswemade tothe 3rdgenerationruntime and itsinteractionwith theportal.13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]] 15 15 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. 15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start. 18 18 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. 17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 21 21 22 -//__Improved migration for JMS flows__// 23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}} 24 24 25 - {{warning}}If youalready migratedyourJMS flowyou shouldexecutea "Reset" action on JMSlevelto get these changes in yourmodel{{/warning}}21 +== **Manage overview Event Streaming** ~*~* == 26 26 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. 23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data. 29 29 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. 25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]] 32 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 namingconventionon Store related pages__//38 -We have imp rovedvariousdisplaynamesto ensure thatitis clearfromthe namingthatstorecontentcan be implementedinallintegrationpatterns.31 +//__Topic configuration calculation__// 32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics. 39 39 40 -//__ Press"Enter"to searchonmultiple pages__//41 - InourDaemonSwitchrelease,we addedfunctionalitythatallowedyouto press**Enter**tosearchon the property overview page.This releasehasaddedthisfunctionalityto manymorepages acrossthe portal. The completelist isas follows.34 +//__Make preparation step in deployment plan visible__// 35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan. 42 42 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 37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 57 57 58 -== **Bug fixes ** == 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. 59 59 60 -//__ LoadingproblemsofDeployment planexecution overview__//61 - Wehavefixedaproblemthatcouldcauseissueswhentryingto showthedeploymentplanexecutionoverview afterpressingtheDeploy buttonin Deploy-> Releases.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. 62 62 45 +//__User Management synchronization now happens in one step__// 46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized. 47 + 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: 66 66 67 -* [[ Synchronousfilepick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]68 -* [[ Receivinge-mail via IMAP orPOP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]69 -* [[ Bestway of Receivingand SendingMail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]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"]] 70 70 71 71 == **Key takeaways** == 72 72