Wiki source code of 227 - Fix Frenzy
Last modified by Carlijn Kokkeler on 2024/08/14 12:51
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!** This release we have many fixes! Mainly for flow testing, the deploy phase, and alerting for hybrid models several small bugs have been resolved. Apart from these fixes, search functionality has been added to the start/stop flows screen. Moreover, the tracing information for errorChannel messages in flow test traces has been improved and we have enabled our new queue trigger functionality for redelivery-enabled messaging queues. Find out all about it below! | ||
| 7 | |||
| 8 | == **Feedback Items** == | ||
| 9 | //__Tracing information__// | ||
| 10 | Tracing errors in flow testing has been improved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V312.WebHome||target="blank"]] is available. | ||
| 11 | |||
| 12 | [[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]] | ||
| 13 | |||
| 14 | //__Start/stop flows search__// | ||
| 15 | It is now possible to search in the Start/Stop flows overview. | ||
| 16 | |||
| 17 | [[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-searchterm.png]] | ||
| 18 | |||
| 19 | //__Message redelivery queue triggers__// | ||
| 20 | The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues. | ||
| 21 | |||
| 22 | == **Bug Fixes** == | ||
| 23 | //__Update namespace resources__// | ||
| 24 | The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions. | ||
| 25 | |||
| 26 | //__Queue triggers hybrid models__// | ||
| 27 | 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 use the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating. | ||
| 28 | |||
| 29 | //__Internal/External recipients__// | ||
| 30 | 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. | ||
| 31 | |||
| 32 | //__Tenant queue trigger__// | ||
| 33 | We have fixed a case where a tenant queue trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime. | ||
| 34 | |||
| 35 | //__Area selector__// | ||
| 36 | We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas. | ||
| 37 | |||
| 38 | //__Runtime overview__// | ||
| 39 | The runtime overview will now always display the correct container version. | ||
| 40 | |||
| 41 | //__List of runtimes__// | ||
| 42 | We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of runtimes that will be restarted. | ||
| 43 | |||
| 44 | //__Deploy prevention__// | ||
| 45 | We have resolved a bug that prevented you from deploying anything on a newly created model. | ||
| 46 | |||
| 47 | //__Cancel button__// | ||
| 48 | The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes. | ||
| 49 | |||
| 50 | //__Log test execution__// | ||
| 51 | If opening a test execution log is not possible during flow testing, a warning message will now be displayed. | ||
| 52 | |||
| 53 | == **Fancy Forum Answers** == | ||
| 54 | |||
| 55 | 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: | ||
| 56 | |||
| 57 | * [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]] | ||
| 58 | * [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]] | ||
| 59 | |||
| 60 | == **Key Takeaways** == | ||
| 61 | |||
| 62 | 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: | ||
| 63 | |||
| 64 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 65 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 66 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 67 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 68 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]] | ||
| 69 | * Start thinking about how the license tracker can aid your development | ||
| 70 | * Start thinking about major, minor, and patch | ||
| 71 | * Keep making great integrations | ||
| 72 | |||
| 73 | Let's stay in touch and till next time! | ||
| 74 | |||
| 75 | {{info}} | ||
| 76 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 77 | |||
| 78 | {{/info}} | ||
| 79 | ))) | ||
| 80 | |||
| 81 | ((( | ||
| 82 | {{toc/}} | ||
| 83 | ))) | ||
| 84 | {{/container}} | ||
| 85 | {{/container}} |