Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 87.1
edited by eMagiz
on 2023/02/28 11:58
Change comment: There is no comment for this version
To version 505.2
edited by CarlijnKokkeler
on 2024/05/06 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +220 - Patch Parade
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,87 +1,91 @@
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 couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **REST XML for API Gateway** ==
8 +== **Feedback Items** ==
8 8  
9 -{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
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.
10 10  
11 -To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
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.
14 14  
15 -Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
18 18  
19 -==**Cloud Template update** ==
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
20 20  
21 -We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set).
22 -
23 -====Cloud Template R23 - Single Lane ====
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
24 24  
25 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
26 26  
27 -====Cloud Template R6 - Single Lane ====
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
28 28  
29 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
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.
30 30  
31 -====Cloud Template R6 - Double Lane====
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
32 32  
33 -This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
38 +//__JMS header handling__//
39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released.
34 34  
35 -== **WS-Security on the 3rd generation runtime** ~*~* ==
41 +== **Bug Fixes** ==
42 +//__Annotation styling__//
43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
36 36  
37 -To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols.
45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
38 38  
39 -== **State Generation ~*~* ==
47 +//__Filter rejection warnings__//
48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
40 40  
41 -With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
42 42  
43 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
52 +//__Manage Explore__//
53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
44 44  
45 -== **Feedback items ** ==
55 +//__Page refreshing__//
56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
46 46  
47 -//__Removed OData as option for an API Gateway operation__//
48 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
58 +//__Message redelivery__//
59 +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.
49 49  
50 -//__Changes in API Gateway operation paths is automatically updated in Create__//
51 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
61 +//__Deployment plan__//
62 +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.
52 52  
53 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
64 +//__Overview pages__//
65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
54 54  
55 -== **Bug fixes ** ==
67 +//__Memory check__//
68 +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.
56 56  
57 -//__Prevent endless loop in Deploy -> User Management__//
58 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
59 -
60 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
61 -
62 -//__Update error handling during migration to the 3rd generation runtime__//
63 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
64 -
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
70 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
71 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
74 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
75 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
76 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
72 72  
73 -== **Key takeaways** ==
78 +== **Key Takeaways** ==
74 74  
75 -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:
80 +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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
86 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a GEN3-only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
96 +{{/info}}
97 +)))
98 +
99 +(((
100 +{{toc/}}
101 +)))
94 94  {{/container}}
103 +{{/container}}