Skip to Content

Changes for page 217 - Template Tango

Last modified by CarlijnKokkeler on 2024/04/23 12:06
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version
To version 410.1
edited by CarlijnKokkeler
on 2024/03/25 10:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +217 - Template Tango
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,53 +1,56 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **3rd generation improvements and bug fixes** ==
8 +== **Cloud Template R12 Docker - Single Lane** ==
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
10 +== **Cloud Template R12 Docker - Single Lane** ==
11 11  
12 -{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
12 +== **Feedback Items** ==
13 +//__Improved event streaming graph__//
14 +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.
13 13  
14 -//__Improved efficiency in deploying a release__//
15 -This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
16 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]]
16 16  
17 -//__Removed specific dependencies between Deploy Architecture and Releases__//
18 -In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
18 +//__Flow versions auto deletion__//
19 +Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available.
19 19  
20 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
21 +== **Bug Fixes** ==
22 +//__Queue name validation__//
23 +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 when editing this in the Create phase in the Flow Designer.
22 22  
23 -//__Improved migration behavior__//
24 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25 -A smoother migration of your JMS (and backup JMS) process.
26 -Shortening of names that otherwise would be too long, additional feedback given to the user.
27 -Feedback when the migration process is finished.
25 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
28 28  
29 -//__Additional checks when deploying__//
30 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
27 +//__Removal of onramp__//
28 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
31 31  
30 +//__eMagiz login__//
31 +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.
32 +
32 32  == **Fancy Forum Answers** ==
33 33  
34 34  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:
35 35  
36 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
37 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
38 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
39 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
40 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
41 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
38 38  
39 -== **Key takeaways** ==
43 +== **Key Takeaways** ==
40 40  
41 -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:
45 +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:
42 42  
43 43  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
44 44  * If you have feedback or ideas for us, talk to the Platypus
45 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46 46  * Clear your browser cache (Ctrl + Shift + Del)
47 47  * Check out the release notes [here]
48 48  * Start thinking about how the license tracker can aid your development
49 49  * Start thinking about major, minor, and patch
50 -* Upgrade to the latest build number
51 51  * Keep making great integrations
52 52  
53 53  Let's stay in touch and till next time!
... ... @@ -55,6 +55,11 @@
55 55  {{info}}
56 56  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  
58 -~*~* Indicates a GEN3-only feature.
59 -{{/info}})))((({{toc/}}))){{/container}}
61 +{{/info}}
62 +)))
63 +
64 +(((
65 +{{toc/}}
66 +)))
60 60  {{/container}}
68 +{{/container}}