Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
Change comment: There is no comment for this version
To version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +198 - Great Migration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,94 +1,53 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
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.
7 7  
8 -== **Pop-up Improvements** ==
9 -//__Property releases__//
10 -When a new property release is created, this property release can now be viewed and deleted.
7 +== **3rd generation improvements and bug fixes** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
13 13  
14 -//__Runtime deletion__//
15 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
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}}
16 16  
17 -//__Wiretap & debug error messages__//
18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
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.
19 19  
20 -//__Action messages__//
21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
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.
22 22  
23 -== **Formatting & Alignments** ==
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.
24 24  
25 -//__Input fields__//
26 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
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.
27 27  
28 -//__UI improvements__//
29 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
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.
30 30  
31 -//__Runtime overview image versions__//
32 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
33 -
34 -//__Component changes reversion__//
35 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
36 -
37 -//__State generation statistics__//
38 -The state generation graphs will now show the correct number of cache hits and misses.
39 -
40 -//__Queue browser timestamps__//
41 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
42 -
43 -//__Addition and deletion of internal recipients__//
44 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
45 -
46 -== **Feedback Items** ==
47 -
48 -//__Update flows__//
49 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
50 -
51 -//__Q&A forum search__//
52 -The option to search by pressing the Enter key has been added to the Q&A forum.
53 -
54 -//__Memory settings__//
55 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
56 -
57 -//__Runtime validation__//
58 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
59 -
60 -
61 -== **Bug Fixes** ==
62 -
63 -//__Removal of onramp__//
64 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
65 -
66 -//__Runtime statistics details__//
67 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
68 -
69 -//__Deployment prechecks__//
70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
71 -
72 -
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
77 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
78 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
79 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
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"]]
80 80  
81 -== **Key Takeaways** ==
39 +== **Key takeaways** ==
82 82  
83 -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:
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:
84 84  
85 85  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
45 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 88  * Clear your browser cache (Ctrl + Shift + Del)
89 89  * Check out the release notes [here]
90 90  * Start thinking about how the license tracker can aid your development
91 91  * Start thinking about major, minor, and patch
50 +* Upgrade to the latest build number
92 92  * Keep making great integrations
93 93  
94 94  Let's stay in touch and till next time!
... ... @@ -96,11 +96,6 @@
96 96  {{info}}
97 97  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98 98  
99 -{{/info}}
100 -)))
101 -
102 -(((
103 -{{toc/}}
104 -)))
58 +~*~* Indicates a GEN3-only feature.
59 +{{/info}})))((({{toc/}}))){{/container}}
105 105  {{/container}}
106 -{{/container}}