Wiki source code of 203 - Fast Paced
Version 145.1 by Erik Bakker on 2023/08/15 11:35
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 4 | |||
| 5 | **Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items. | ||
| 6 | |||
| 7 | == **Release Properties - Early Feedback** == | ||
| 8 | The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties. | ||
| 9 | |||
| 10 | == **Feedback Items** == | ||
| 11 | |||
| 12 | //__"All entries" are now cleaned up as part of the migration__// | ||
| 13 | To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture. | ||
| 14 | |||
| 15 | //__Trigger ID added to our alerting on the next-generation architecture__// | ||
| 16 | We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable. | ||
| 17 | |||
| 18 | == **Bug Fixes** == | ||
| 19 | |||
| 20 | //__Ensure no flow can be in a release twice__// | ||
| 21 | We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this. | ||
| 22 | |||
| 23 | //__Ensure no flow can be in a release twice__// | ||
| 24 | We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this. | ||
| 25 | |||
| 26 | == **Fancy Forum Answers** == | ||
| 27 | |||
| 28 | 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: | ||
| 29 | |||
| 30 | * [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] | ||
| 31 | |||
| 32 | == **Key takeaways** == | ||
| 33 | |||
| 34 | Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: | ||
| 35 | |||
| 36 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 37 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 38 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 39 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 40 | * Check out the release notes [here] | ||
| 41 | * Start thinking about how the license tracker can aid your development | ||
| 42 | * Start thinking about major, minor, and patch | ||
| 43 | * Upgrade to the latest build number | ||
| 44 | * Keep making great integrations | ||
| 45 | |||
| 46 | Let's stay in touch and till next time! | ||
| 47 | |||
| 48 | {{info}} | ||
| 49 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 50 | |||
| 51 | ~*~* Indicates a next-generation-architecture only feature. | ||
| 52 | {{/info}})))((({{toc/}}))){{/container}} | ||
| 53 | {{/container}} |