Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
Change comment: There is no comment for this version
To version 402.1
edited by Erik Bakker
on 2024/02/27 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +215 - Tiny Tales
Content
... ... @@ -1,49 +1,47 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 +
6 +**Hi there, eMagiz developers!** This release blog is small because we have been busy working on items that will be released later. For this release, the event streaming graph has been improved. Moreover, some bug fixes have been done. The validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
4 4  
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.
6 -
7 7  == **Feedback Items** ==
9 +//__Improved event streaming graph__//
10 +The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic.
8 8  
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.
12 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics.png]]
11 11  
12 -//__Removed outdated properties when deploying on the new generation architecture stack__//
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 connecting to a Kafka cluster but have become obsolete once you migrate.
14 -
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 -
17 -//__Improved performance Manage Dashboards__//
18 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
19 -
20 20  == **Bug Fixes** ==
15 +//__Queue name validation__//
16 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name.
21 21  
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).
18 +//__Removal of onramp__//
19 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible.
24 24  
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.
21 +//__eMagiz login__//
22 +In the login screen, users can now "press enter" to log in when the username field is selected. Previously, this was only the case for the password field.
27 27  
28 28  == **Fancy Forum Answers** ==
29 29  
30 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:
31 31  
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"]]
28 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
29 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
30 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
31 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
32 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
34 34  
35 -== **Key takeaways** ==
34 +== **Key Takeaways** ==
36 36  
37 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:
38 38  
39 39  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40 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.
40 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
42 42  * Clear your browser cache (Ctrl + Shift + Del)
43 43  * Check out the release notes [here]
44 44  * Start thinking about how the license tracker can aid your development
45 45  * Start thinking about major, minor, and patch
46 -* Upgrade to the latest build number
47 47  * Keep making great integrations
48 48  
49 49  Let's stay in touch and till next time!
... ... @@ -51,6 +51,11 @@
51 51  {{info}}
52 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 53  
54 -~*~* Indicates a next-generation-architecture only feature.
55 -{{/info}})))((({{toc/}}))){{/container}}
52 +{{/info}}
53 +)))
54 +
55 +(((
56 +{{toc/}}
57 +)))
56 56  {{/container}}
59 +{{/container}}