Wiki source code of 204 - Found It

Last modified by Carlijn Kokkeler on 2024/04/18 13:12

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 149.1 5 **Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
eMagiz 1.1 6
Erik Bakker 133.1 7 == **Feedback Items** ==
Erik Bakker 101.1 8
Erik Bakker 149.1 9 //__Improved check on nested property placeholders__//
10 To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
Erik Bakker 124.1 11
Erik Bakker 149.1 12 //__Removed outdated properties when deploying on the new generation architecture stack__//
Erik Bakker 150.1 13 We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
Erik Bakker 124.1 14
Erik Bakker 149.1 15 {{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
16
Erik Bakker 146.1 17 //__Improved performance Manage Dashboards__//
Erik Bakker 149.1 18 We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
Erik Bakker 146.1 19
Erik Bakker 124.1 20 == **Bug Fixes** ==
Erik Bakker 122.1 21
Erik Bakker 149.1 22 //__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
Erik Bakker 119.1 24
Erik Bakker 149.1 25 //__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
Erik Bakker 148.1 27
eMagiz 1.1 28 == **Fancy Forum Answers** ==
29
Erik Bakker 30.1 30 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 31
Erik Bakker 149.1 32 * [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 * [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
eMagiz 1.1 34
Carlijn Kokkeler 151.1 35 == **Key Takeaways** ==
eMagiz 1.1 36
Erik Bakker 149.1 37 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:
eMagiz 1.1 38
Erik Bakker 30.1 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 40 * If you have feedback or ideas for us, talk to the Platypus
41 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
42 * Clear your browser cache (Ctrl + Shift + Del)
Carlijn Kokkeler 152.1 43 * Check out the release notes [[here>>doc:Main.Release Information.Portal.204 - Found It.WebHome||target="blank"]]
eMagiz 1.1 44 * Start thinking about how the license tracker can aid your development
45 * Start thinking about major, minor, and patch
46 * Upgrade to the latest build number
47 * Keep making great integrations
48
49 Let's stay in touch and till next time!
50
51 {{info}}
Erik Bakker 30.1 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]]
eMagiz 1.1 53
Erik Bakker 141.1 54 ~*~* Indicates a next-generation-architecture only feature.
eMagiz 1.1 55 {{/info}})))((({{toc/}}))){{/container}}
56 {{/container}}