Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** | ||
| 7 | |||
| 8 | == **Feedback Items** == | ||
| 9 | //__Start/stop flows search__// | ||
| 10 | The user is now able to search in the Start/Stop flows overview. | ||
| 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 | [[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]] | ||
| 18 | |||
| 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 | |||
| 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 | == **Fancy Forum Answers** == | ||
| 30 | |||
| 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 | |||
| 33 | * [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]] | ||
| 34 | * [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]] | ||
| 35 | |||
| 36 | == **Key Takeaways** == | ||
| 37 | |||
| 38 | 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: | ||
| 39 | |||
| 40 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 41 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 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 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 44 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]] | ||
| 45 | * Start thinking about how the license tracker can aid your development | ||
| 46 | * Start thinking about major, minor, and patch | ||
| 47 | * Keep making great integrations | ||
| 48 | |||
| 49 | Let's stay in touch and till next time! | ||
| 50 | |||
| 51 | {{info}} | ||
| 52 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 53 | |||
| 54 | {{/info}} | ||
| 55 | ))) | ||
| 56 | |||
| 57 | ((( | ||
| 58 | {{toc/}} | ||
| 59 | ))) | ||
| 60 | {{/container}} | ||
| 61 | {{/container}} |