Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 110.1
edited by Erik Bakker
on 2023/05/05 10:25
on 2023/05/05 10:25
Change comment:
There is no comment for this version
To version 260.1
edited by Carlijn Kokkeler
on 2023/11/22 14:55
on 2023/11/22 14:55
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 - 196-The LastPost1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,76 +1,77 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In thelast fewweeks,wehaveworkhardonimprovingournextgenerationarchitectureandintroducedthe"live"modewithin ourflow testingfunctionality.Furthermorethereare loads ofsmaller feedback items and bugsthat have beenresolvedwiththis release.So withoutfurtherdolets dive into allwehave tooffer.6 +**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default. 6 6 7 -== **"Live" mode on flow testing** == 8 +{{warning}} 9 +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 6:00 AM UTC instead of 5:00 AM UTC. 10 +{{/warning}} 8 8 9 - Withthis release we bringan improved version of the flow testing functionality. As of now you will havethe optionoswitch between "live"and"mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all externalcommunicationis mocked by the system and only the functional process can be tested.12 +== **Quicker Deployment Plan Execution** == 10 10 11 - Byswitching to "live"modeyou cannot onlytest thefunctionalprocessbut alsothe communicationtothe external system.Youcanosoby enteringthe"edit"modeoftheflowtest andtogglebetween"mock"and"live" mode.When doingso eMagizwill showyou thefollowingpop-upstressingtheconsequencesof youractions.14 +We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now! 12 12 13 - [[image:Main.Images.ReleaseBlog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]16 +== **Next Generation Architecture Default** == 14 14 15 - Onceconfirmed you willseethattheuserrfacenowndicatesthattheendpointis in"live"mode.18 +With this release, the next generation architecture will become the default. New models will use this generation as default. 16 16 17 -[[image:Main.Images.Release Blog.WebHome@ 196-release-blog--live-flow-testing-result.png]]20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]] 18 18 19 -{{info}}* The following restrictions apply for this functionality 20 - ** "Live" mode can only be activated on HTTP outbound gateway components 21 - ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/info}} 22 +== **Cloud Template R11 Docker - Single Lane** == 22 22 23 - ==**3rd generation improvements**==24 +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>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]]. 24 24 25 -//__Event Streaming statistics completion__// 26 -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. 26 +== **Cloud Template R13 Docker - Double Lane** == 27 27 28 -//__Deployments on next generation architecture__// 29 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture. 28 +This release introduces a new cloud template for all our customers running in a double-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>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 30 30 31 -//__Clean queues option__// 32 -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. 30 +== **Feedback Items** == 33 33 34 -== **Feedback items ** == 32 +//__Unused properties overview__// 33 +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: 35 35 36 -//__On-premise containers are started upon slot wakeup__// 37 -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. 35 +* Not used by any runtime that is in the Create phase release. 36 +* Not required by a flow that is in the Create phase release. 37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 38 38 39 -//__ Resource pathisshownto the user__//40 - You can now, without downloading, seetheresourcepath of aresourceby viewingthe metadataof the resource. Youcanosoby pressingthe"eye" iconto view thisinformation.39 +//__Queue explorer milliseconds__// 40 +The queue browser now displays milliseconds in the timestamps. 41 41 42 -//__ Flow designerimprovements__//43 -W iththisreleasevariousimprovements havebeen madeto theflow designer. Among others we haveimprovedthe overview of what an "unusedresource"is. Younowhavethe optionto define certain resourcesthat are used butcannot beauto-detected by eMagiztobean "used"resource to avoidconfusion.42 +//__Unused images__// 43 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 44 44 45 -//__ Improved capabilities of a company contact__//46 - Withthis releasewehave improvedthecapabilities of a companycontact. As of now youcan alsoadd usersto modelsbelongingtosubcompaniesbelowyourthe companytowhichyouarethecompany contact.45 +//__Carwash logging__// 46 +A new logging feature enabling us to make better choices in encryption standards will be released. 47 47 48 -== **Bug fixes ** == 48 +//__Static alerts queue consumers__// 49 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 49 49 50 -//__Optional API parameters are handled correctly__// 51 -Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box. 51 +== **Bug Fixes** == 52 52 53 -//__ WithoutCDM rightsnothingrelatedtoany data modelcanbe edited anymore__//54 - Withthis release,we havemadesure thatnothingrelatedto anydata modelcanbeedited withouthavingtheproperrights.53 +//__Flow Designer connection line__// 54 +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. 55 55 56 -//__ Improved sortingofDesignandDeploy archticture__//57 -W iththisrelease,we nowensurethatbothDesign andDeploy architectureare sortedin thesamemannertoavoidconfusionwhenquicklyswitchingbetweenbothviews.56 +//__Portal for migrated models__// 57 +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. 58 58 59 +//__Error channel inbounds__// 60 +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. 61 + 59 59 == **Fancy Forum Answers** == 60 60 61 61 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: 62 62 63 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 64 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]] 65 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]] 66 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 66 66 67 67 == **Key takeaways** == 68 68 69 -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:70 +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: 70 70 71 71 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 72 72 * If you have feedback or ideas for us, talk to the Platypus 73 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 74 74 * Clear your browser cache (Ctrl + Shift + Del) 75 75 * Check out the release notes [here] 76 76 * Start thinking about how the license tracker can aid your development ... ... @@ -83,6 +83,12 @@ 83 83 {{info}} 84 84 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 85 85 86 -~*~* Indicates a GEN3-only feature. 87 -{{/info}})))((({{toc/}}))){{/container}} 87 +~*~* Indicates a next-generation-architecture only feature. 88 +{{/info}} 89 +))) 90 + 91 +((( 92 +{{toc/}} 93 +))) 88 88 {{/container}} 95 +{{/container}}