Skip to Content

Changes for page 222 - Flee Frustration

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +198 - Great Migration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,67 +1,60 @@
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!** In this release, we improve the user interface for managing your failover and grouping configurations and improved the method for adding new attributes to data models. Next to this, we have improved the Event Catalog overview for Catalog users. Using the back button on the eMagiz Q&A now also brings you back to where you were with your search query. We also fixed some previous bugs, resulting in improved delete behavior for containers and correctly generated scope properties. Lastly, there will not be a warning message anymore when importing an XSD if there is no selected request or response message definition.
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.
7 7  
8 -== **Feedback Items** ==
9 -//__Q&A search__//
10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A.
7 +== **3rd generation improvements and bug fixes** ==
11 11  
12 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
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 -//__Attribute placements__//
18 -Some improvements regarding the placement of attributes have been done:
19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
20 -* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with.
21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
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.
24 24  
25 -//__Failover & grouping__//
26 -Some improvements regarding the widgets for failover and grouping have been done:
27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
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.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
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.
33 33  
34 -== **Bug Fixes** ==
35 -//__XSD import__//
36 -When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion.
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}}
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
31 +== **Feedback items ** ==
39 39  
40 -//__Container deletion__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
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.
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
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.
45 45  
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
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"]]
53 53  
54 -== **Key Takeaways** ==
46 +== **Key takeaways** ==
55 55  
56 -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:
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:
57 57  
58 58  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
54 +* Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
57 +* Upgrade to the latest build number
65 65  * Keep making great integrations
66 66  
67 67  Let's stay in touch and till next time!
... ... @@ -69,11 +69,6 @@
69 69  {{info}}
70 70  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  
72 -{{/info}}
73 -)))
74 -
75 -(((
76 -{{toc/}}
77 -)))
65 +~*~* Indicates a GEN3-only feature.
66 +{{/info}})))((({{toc/}}))){{/container}}
78 78  {{/container}}
79 -{{/container}}