Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
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 279.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
on 2023/12/04 14:54
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-TheLastPost1 +209 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,75 +1,64 @@ 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 few weeks, wehavework hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality.Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release.So without further ado let us dive into all we have to offer.6 +**Hi there, eMagiz developers!** We have... 6 6 7 -== ** "Live" modeonflowtesting** ==8 +== **Release Maintenance** == 8 8 9 -With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch 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 external communication is mocked by the system and only the functional process can be tested. 10 10 11 -By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]] 14 14 15 -Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode. 16 16 17 - [[image:Main.Images.ReleaseBlog.WebHome@196-release-blog--live-flow-testing-result.png]]14 +== **Feedback Items** == 18 18 19 -== **3rd generation improvements** == 16 +//__Container version overview__// 17 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 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. 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 23 23 24 -//__ Deployments onnextgenerationrchitecture__//25 - Thisreleasefixesseveralsmallerbugs andaddsseveral improvementsto the deploymentprocessofthe nextgeneration architecture.21 +//__Unchanged containers__// 22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 26 26 27 -//__ Cleanqueuesoption__//28 - This releaseintroducesan option for **admins**toclean queues thatremainedaftera migrationtowardsthenextgenerationruntimearchitecture.Thiswillmakethe overviewof which queuesare"problematic"a much morerealistic overview.24 +//__Rebuilding of images__// 25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 29 29 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. 28 +== **Bug Fixes** == 34 34 35 -//__ See FixedIPinDeploy Architecture__//36 -T o improveourcloud offerings'wenowdisplay the configuredfixedIP on yourcloud connectors.Thiswill unlockyou as theuserto easilymmunicatethis value toexternal parties withoutinvolvementon our end.30 +//__Runtime metrics processing__// 31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 37 37 38 -//__ Resource path is shownto the user__//39 - Youcannow, without downloading,see thesourcepathof a resource byviewingthemetadataoftheresource.Youcanso bypressingthe"eye" icontoview thisinformation.33 +//__Deployment plan__// 34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 40 40 41 -//__ Flowdesignerimprovements__//42 - Withthis releasevarious improvementshavebeenmade tothe flowdesigner.Amongotherswehaveimprovedtheoverview ofwhatan"unusedresource"is. You now havetheoptiontodefine certainresources thatreused but cannot be auto-detectedbyeMagiz to bean "used" resource to avoid confusion.36 +//__Store message merging__// 37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 43 43 44 -//__ Improvedcapabilitiesof a company contact__//45 - Withthisreleasewehave improvedthecapabilitiesofacompany contact.As ofnow you can alsoduserstomodelsbelongingtosubcompanies belowyourthecompany to which you arehecompanycontact.39 +//__View all store items__// 40 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 46 46 47 -== **Bug fixes ** == 42 +//__Out of memory behavior__// 43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 48 48 49 -//__Optional API parameters are handled correctly__// 50 -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. 45 +//__Max fetch size__// 46 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 47 + 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 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 63 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]] 64 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]] 53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 65 65 66 66 == **Key takeaways** == 67 67 68 -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:57 +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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 74 * Check out the release notes [here] 75 75 * Start thinking about how the license tracker can aid your development ... ... @@ -82,6 +82,12 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a GEN3-only feature. 86 -{{/info}})))((({{toc/}}))){{/container}} 74 +~*~* Indicates a next-generation-architecture only feature. 75 +{{/info}} 76 +))) 77 + 78 +((( 79 +{{toc/}} 80 +))) 87 87 {{/container}} 82 +{{/container}}