Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 243.1
edited by Carlijn Kokkeler
on 2023/11/21 11:31
on 2023/11/21 11:31
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 - 192 -SmallStep1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,64 +2,79 @@ 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 thelast couple of weeks we workedhard on building severalmajor things that will be releasedlater this Q. On top of that we finishedan 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.5 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 -== **Start/Stop Flows** ~*~* == 7 +{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 8 +6:00 AM UTC instead 5:00 AM UTC. {{/warning}} 8 8 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 +== **Next Generation Architecture Default** == 11 +With this release, the next generation architecture will become the default. New models will use this generation as default. 10 10 11 - To enhance the options you have when runninginto problems or when maintainingyour solution in a Productionenvironment, we have added a new feature to our Deploy phasecalled "Start/Stop Flows". You can accessthis functionality via the "Deploy Architecture"overview in Deploy. On runtimelevelyou canopen the contextmenu andselect the option called "Start/Stop Flows".13 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 12 12 13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]] 15 +== **Cloud Template R11 - Single Lane** == 16 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here 14 14 15 - Afterselecting theoption eMagiz will open a pop-up in which you can stop andstart the starting point of each flow that is deployed on that runtime.Theeffect of this is that no newmessages will beprocessed by the flow butall remaining messages will still beprocessedbythe flow after stopping the flow. To stop a flow yousimply selectaflow and pressthe Stop button. To start it again press Start.18 +== **Cloud Template R13 - Double Lane** == 16 16 17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 18 18 19 - {{info}}Onlyin "Start Editing" modeyou can actuallystart and stop specific flows{{/info}}21 +== **Feedback Items** == 20 20 21 -== **Manage overview Event Streaming** ~*~* == 23 +//__Unused properties overview__// 24 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 25 +* Not used by any runtime that is in the Create phase release. 26 +* Not required by a flow that is in the Create phase release. 27 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 22 22 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 +//__Send build requests asynchronously__// 30 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]] 32 +//__Queue explorer milliseconds__// 33 +The queue browser now displays milliseconds in the timestamps. 26 26 27 -== **Feedback items ** == 35 +//__Cancel and next buttons order__// 36 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 28 28 29 -We have also solved other feedback items besides the flow designer's critical updates. 38 +//__Unused images__// 39 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 30 30 31 -//__ Topic configurationcalculation__//32 - Withthis releasewehave simplifiedtheconfigurationofsettingsontopicleveltoenforcecertain best practiceswithinthertal andt thesametimemakeiteasier to configure topics.41 +//__Carwash logging__// 42 +A new logging feature enabling us to make better choices in encryption standards will be released. 33 33 34 -//__ Makepreparationstepin deploymentplanvisible__//35 - Fora deploymentonthe 3rdgeneration runtimeto work somepreparationworkneeds to be done by the portal.Wehave nowmadethisstepexplicitandpart of thedeployment plan.44 +//__Static alerts queue consumers__// 45 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 36 36 37 - {{warning}}Makesure to update your deployment plan accordinglyto ensure that the preparation step isnot forgotten{{/warning}}47 +== **Bug Fixes** == 38 38 39 -//__ 3rdgenerationruntimedebugger feedback__//40 -We haveimprovedtheuserexperienceofthe3rd generationruntimedebuggerwiththisrelease bysolvingvariousfeedbackitemswenoticed inhefirstadoptions ofthefunctionality.49 +//__Images rebuild__// 50 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped. 41 41 42 -//__ No"Shift key"needed anymoretoselectmultiple items inthe flow designer__//43 - As ofnowyou do notaveto hold your"Shift key"whenyouwant toselectmultipleitemsinthe flowdesigner.Thiswillmakeit easier toselectpartsof flows.52 +//__Flow Designer connection line__// 53 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 44 44 45 -//__ UserManagementsynchronizationnowhappensinonetep__//46 -W iththisrelease wehaveupdatedthe synchronizationprocessbetweenDesignandDeploywithregards toUserManagement. Fromnowon,whenyoupressthe"Transferfromdesign"buttonbothUsersandRoleswill besynchronized.55 +//__Portal for migrated models__// 56 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 47 47 58 +//__Error channel inbounds__// 59 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 60 + 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"]] 65 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 66 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 67 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 68 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 55 55 70 + 56 56 == **Key takeaways** == 57 57 58 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:73 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 77 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 64 * Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development ... ... @@ -72,6 +72,6 @@ 72 72 {{info}} 73 73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 75 -~*~* Indicates a GEN3-only feature.90 +~*~* Indicates a next-generation-architecture only feature. 76 76 {{/info}})))((({{toc/}}))){{/container}} 77 77 {{/container}}