Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
Change comment: There is no comment for this version
To version 505.1
edited by CarlijnKokkeler
on 2024/05/06 13:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +220 - Patch Parade
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,60 +1,88 @@
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 as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **3rd generation improvements and bug fixes** ==
8 +== **Feedback Items** ==
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 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
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}}
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
13 13  
14 -//__Removed certain dependencies between Deploy Architecture and Releases__//
15 -In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
16 16  
17 -//__Improved validation errors on invalid configuration of HTTP outbound components__//
18 -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.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19 19  
20 -//__Improved migration behavior__//
21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
22 22  
23 -//__Improved auto-healing when running in a hybrid situation__//
24 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
25 25  
26 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
27 -To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
28 28  
29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
30 30  
31 -== **Feedback items ** ==
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32 32  
33 -//__Make sure the message format can be viewed without "Start editing"__//
34 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
35 35  
36 -//__Various styling improvements in the flow testing functionality__//
37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
38 38  
38 +== **Bug Fixes** ==
39 +//__Annotation styling__//
40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
41 +
42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
43 +
44 +//__Filter rejection warnings__//
45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
46 +
47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
48 +
49 +//__Manage Explore__//
50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
51 +
52 +//__Page refreshing__//
53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
54 +
55 +//__Message redelivery__//
56 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
57 +
58 +//__Deployment plan__//
59 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
60 +
61 +//__Overview pages__//
62 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
63 +
64 +//__Memory check__//
65 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
66 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
44 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
71 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
72 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
73 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
45 45  
46 -== **Key takeaways** ==
75 +== **Key Takeaways** ==
47 47  
48 -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:
77 +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:
49 49  
50 50  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [here]
83 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
57 -* Upgrade to the latest build number
58 58  * Keep making great integrations
59 59  
60 60  Let's stay in touch and till next time!
... ... @@ -62,6 +62,11 @@
62 62  {{info}}
63 63  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64 64  
65 -~*~* Indicates a GEN3-only feature.
66 -{{/info}})))((({{toc/}}))){{/container}}
93 +{{/info}}
94 +)))
95 +
96 +(((
97 +{{toc/}}
98 +)))
67 67  {{/container}}
100 +{{/container}}