Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 106.1
edited by Erik Bakker
on 2023/04/25 13:59
on 2023/04/25 13:59
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -19 6-The LastPost1 +192 - Small Step - Content
-
... ... @@ -2,66 +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!** In the last fewweeks, wehavework hard on improvingournext generationarchitecturendintroducedthe "live"modewithin ourflowtestingfunctionality.Furthermorethereare loadsof smaller feedback items andbugsthathavebeenresolvedwiththisrelease.Sowithout furtheradoletus dive intoallwehave to offer.5 +**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform. 6 6 7 -== ** "Live" modeon flowtesting** ==7 +== **Start/Stop Flows** ~*~* == 8 8 9 - With this releasewe bring animprovedversion oftheflow testingfunctionality.As of nowyou willhave theoptiontoswitchbetween"live" and "mock"modewillrunninga flowtest. The"mock" modeis themodeyou are usedtofromus. Inhismodell external communicationis mocked by the system and only the functional process can be tested.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}} 10 10 11 - By switching to"live"modeyoucan notonlytestthefunctionalprocess butalsothecommunicationtothe externalsystem. You candosoby enteringthe"edit"mode oftheflowtestand togglebetween"mock" and"live" mode.Whendoing so eMagizwillshowyouthe followingpop-up stressingthe consequencesofyouractions.11 +To enhance your options 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 the runtime level, you can open the context menu and select the "Start/Stop Flows" option. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@19 6-release-blog--live-flow-testing-pop-up.png]]13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]] 14 14 15 - Once confirmedyouwillsee that theuser interfacenowindicates that the endpoint is in"live"mode.15 +After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no 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. 16 16 17 -[[image:Main.Images.Release Blog.WebHome@19 6-release-blog--live-flow-testing-result.png]]17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 18 18 19 - ==**3rd generationimprovements**==19 +{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}} 20 20 21 -//__Event Streaming statistics completion__// 22 -In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment. 21 +== **Manage overview Event Streaming** ~*~* == 23 23 24 -//__Deployments on next generation architecture__// 25 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture. 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 streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data. 26 26 27 -//__Clean queues option__// 28 -This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview. 25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]] 29 29 30 30 == **Feedback items ** == 31 31 32 -//__On-premise containers are started upon slot wakeup__// 33 -With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning. 29 +We have also solved other feedback items besides the flow designer's critical updates. 34 34 35 -//__ See FixedIPinDeploy Architecture__//36 - Toimproveourcloud offerings'wenowdisplaythe configured fixed IPonyourcloudconnectors. Thiswillunlockyou as theuseroeasilycommunicate thisvaluetoexternalpartieswithoutinvolvement onournd.31 +//__Topic configuration calculation__// 32 +With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics. 37 37 38 -//__ Resourcehis shown totheuser__//39 - Youcan now, withoutdownloading,seethe resourcepathofaresourcebyviewingthemetadataof the resource.Youcan dosoby pressingthe"eye"icon toviewthisinformation.34 +//__Make preparation step in deployment plan visible__// 35 +For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan. 40 40 41 -//__Flow designer improvements__// 42 -With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion. 37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 43 43 44 -//__ Improvedcapabilitiesof a companycontact__//45 -W ith this releasewehave improved thecapabilitiesofacompanycontact. Asofnowyoucanalso adduserstomodels belongingtosubcompaniesbelowyourthecompanytowhich youarethecompanycontact.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 46 47 -== **Bug fixes ** == 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 48 49 -//__ OptionalAPI parametersarehandledcorrectly__//50 - Currently, eMagizwouldcreate thewrongexpressionfor handlingoptionalAPIparameters. Withthisreleasewehaveimprovedtheexpressionin such a waythatalloptionalparameters are handledcorrectlyout of thebox.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. 51 51 52 -//__Without CDM rights nothing related to any data model can be edited anymore__// 53 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights. 54 - 55 -//__Improved sorting of Design and Deploy archticture__// 56 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views. 57 - 58 58 == **Fancy Forum Answers** == 59 59 60 60 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: 61 61 62 -* [[ jsonPathinSpELexpressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]63 -* [[ ConnectingtoAzureSQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]64 -* [[ Changes to JSONapi keep breaking my modelvalidation,although they areirrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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"]] 65 65 66 66 == **Key takeaways** == 67 67