Wiki source code of 203 - Fast Paced

Version 144.1 by Erik Bakker on 2023/08/15 10:23

Hide last authors
eMagiz 1.1 1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4
Erik Bakker 144.1 5 **Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
eMagiz 1.1 6
Erik Bakker 144.1 7 == **Release Properties - Early Feedback** ==
8 The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
Erik Bakker 97.1 9
Erik Bakker 133.1 10 == **Feedback Items** ==
Erik Bakker 101.1 11
Erik Bakker 144.1 12 //__"All entries" are now cleaned up as part of the migration__//
13 To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
Erik Bakker 124.1 14
Erik Bakker 144.1 15 //__Trigger ID added to our alerting on the next-generation architecture__//
16 We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
Erik Bakker 124.1 17
18 == **Bug Fixes** ==
Erik Bakker 122.1 19
Erik Bakker 144.1 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.
Erik Bakker 119.1 22
Erik Bakker 144.1 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.
Erik Bakker 120.1 25
eMagiz 1.1 26 == **Fancy Forum Answers** ==
27
Erik Bakker 30.1 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:
eMagiz 1.1 29
Erik Bakker 137.1 30 * [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
eMagiz 1.1 31
32 == **Key takeaways** ==
33
Erik Bakker 30.1 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:
eMagiz 1.1 35
Erik Bakker 30.1 36 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 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}}
Erik Bakker 30.1 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]]
eMagiz 1.1 50
Erik Bakker 141.1 51 ~*~* Indicates a next-generation-architecture only feature.
eMagiz 1.1 52 {{/info}})))((({{toc/}}))){{/container}}
53 {{/container}}