Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 652.1
edited by Carlijn Kokkeler
on 2024/08/12 11:13
on 2024/08/12 11:13
Change comment:
There is no comment for this version
To version 674.1
edited by Carlijn Kokkeler
on 2024/08/26 12:08
on 2024/08/26 12:08
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 7- TBD1 +228 - TBD - Content
-
... ... @@ -3,35 +3,26 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 6 +**Hi there, eMagiz developers!** This release 7 7 8 8 == **Feedback Items** == 9 -//__Start/stop flows search__// 10 -The user is now able to search in the Start/Stop flows overview. 9 +//__Legacy properties__// 10 +We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. 11 + 12 +//__Grafana improvements__// 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]] 13 - 14 -//__Tracing information__// 15 -The tracing information for errorChannel messages in flow test traces has been improved. 16 - 17 17 [[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]] 18 18 16 + 17 + 19 19 == **Bug Fixes** == 20 -//__Update namespace resources__// 21 -The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes on your namespaces in your message definitions. 22 22 23 -//__Queue triggers hybrid models__// 24 -We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating. 25 - 26 -//__Internal/External recipients__// 27 -You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly. Cases where this was applied incorrectly have been automatically fixed. 28 - 29 29 == **Fancy Forum Answers** == 30 30 31 31 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: 32 32 33 -* [[no output-channel orplyChannelheaderavailable>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]34 -* [[l ast flow unknown error with SFTP connectionin Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]24 +* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]] 25 +* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]] 35 35 36 36 == **Key Takeaways** == 37 37 ... ... @@ -41,7 +41,7 @@ 41 41 * If you have feedback or ideas for us, talk to the Platypus 42 42 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 43 43 * Clear your browser cache (Ctrl + Shift + Del) 44 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 6-AlertingAlchemy.WebHome||target="blank"]]35 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]] 45 45 * Start thinking about how the license tracker can aid your development 46 46 * Start thinking about major, minor, and patch 47 47 * Keep making great integrations