Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
on 2023/05/22 15:07
Change comment:
There is no comment for this version
To version 464.1
edited by CarlijnKokkeler
on 2024/04/23 10:37
on 2024/04/23 10:37
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 -19 8-GreatMigration1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,53 +1,57 @@ 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 the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.6 +**Hi there, eMagiz developers!** 6 6 7 -== **3rd generation improvements and bug fixes** == 8 8 9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__// 10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed. 9 +== **Feedback Items** == 10 +//__Machine agents__// 11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more here. 11 11 12 -{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}} 13 +//__Custom webhook__// 14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more here. 13 13 14 -//__ Improvedefficiency indeploying arelease__//15 - Thisreleaseimprovesthe efficiencyofthe "preparerelease"stepneededwhendeployingonthenext-generation architecture.16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4 16 16 17 -//__ Removedspecific dependenciesbetween Deploy Architecture and Releases__//18 - In this release,we haveremoved severalexplicit dependenciesthatconfusedthefunctionalityin the Deploy Architectureoverview comparedtothefunctionalitylinked to arelease, specifically the deploymentofarelease.19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 19 19 20 -//__Improved validation errors on the invalid configuration of HTTP outbound components__// 21 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup. 22 +== **Bug Fixes** == 23 +//__Error handling__// 24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 22 22 23 -//__Improved migration behavior__// 24 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 25 -A smoother migration of your JMS (and backup JMS) process. 26 -Shortening of names that otherwise would be too long, additional feedback given to the user. 27 -Feedback when the migration process is finished. 26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 28 28 29 -//__ Additionalchecks when deploying__//30 - This release introduces additional checks when deploying.Amongothers, we have added a checktopreventyoufromdeploying two flows thatuse thesameresource with differingversions. Not stopping this can cause issueswith deployments and even worsewith the functionalbehavior oftheflows,asit leads to the situation inwhich a validationerror might trigger on one offramp but not on the other.29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 31 31 32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 34 + 32 32 == **Fancy Forum Answers** == 33 33 34 34 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: 35 35 36 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 37 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]] 40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]] 41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]] 42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]] 38 38 39 -== **Key takeaways** ==44 +== **Key Takeaways** == 40 40 41 -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:46 +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: 42 42 43 43 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 44 44 * If you have feedback or ideas for us, talk to the Platypus 45 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 46 46 * Clear your browser cache (Ctrl + Shift + Del) 47 -* Check out the release notes [here] 52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 48 48 * Start thinking about how the license tracker can aid your development 49 49 * Start thinking about major, minor, and patch 50 -* Upgrade to the latest build number 51 51 * Keep making great integrations 52 52 53 53 Let's stay in touch and till next time! ... ... @@ -55,6 +55,11 @@ 55 55 {{info}} 56 56 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 58 -~*~* Indicates a GEN3-only feature. 59 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 60 60 {{/container}} 69 +{{/container}}