Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 09-DeploymentDelights1 +221 - Swift Shift - Content
-
... ... @@ -3,43 +3,29 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** We have...6 +**Hi there, eMagiz developers!** 7 7 8 -== **Release Maintenance** == 9 - 10 - 11 - 12 - 13 - 14 14 == **Feedback Items** == 9 +//__Q&A search__// 10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A. 15 15 16 -//__ Containerversion overview__//17 - In Deploy> Releases,itisnowpossible to see thecontainerversions intherelease details.This can beviewedbyclickingthethreedotsintheCreate phasesection.12 +//__Event catalog__// 13 +We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 18 18 19 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 20 20 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. 23 - 24 -//__Rebuilding of images__// 25 -Changing the list of flows that should run on a container will now trigger the rebuilding of images. 26 - 27 - 28 28 == **Bug Fixes** == 17 +//__XSD import__// 18 +When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. 19 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 29 29 30 -//__Runtime metrics processing__// 31 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 32 - 33 -//__Deployment plan__// 34 -We solved a bug where a deployment step in the deployment plan could randomly get stuck. 35 - 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 25 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 26 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]] 41 41 42 -== **Key takeaways** ==28 +== **Key Takeaways** == 43 43 44 44 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: 45 45 ... ... @@ -47,10 +47,9 @@ 47 47 * If you have feedback or ideas for us, talk to the Platypus 48 48 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 49 * Clear your browser cache (Ctrl + Shift + Del) 50 -* Check out the release notes [here] 36 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]] 51 51 * Start thinking about how the license tracker can aid your development 52 52 * Start thinking about major, minor, and patch 53 -* Upgrade to the latest build number 54 54 * Keep making great integrations 55 55 56 56 Let's stay in touch and till next time! ... ... @@ -58,7 +58,6 @@ 58 58 {{info}} 59 59 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 60 60 61 -~*~* Indicates a next-generation-architecture only feature. 62 62 {{/info}} 63 63 ))) 64 64