Changes for page 207 - Aligned State

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-193 - Fan Out
	1	+203 - Fast Paced

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Content

...	...	@@ -2,73 +2,35 @@
2	2	{{container layoutStyle="columns"}}(((
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.
	5	+**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
6	6
7		-== **REST XML for API Gateway** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
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	+== **Feedback Items** ==
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.
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
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	+//__Improved performance Manage Dashboards__//
	19	+We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
	21	+== **Bug Fixes** ==
18	18
19		-==**Cloud Template update** ==
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
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 ====
	26	+//__Ensure no flow can be in a release twice__//
	27	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
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"]]
26		-
27		-====Cloud Template R6 - Single Lane ====
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"]]
30		-
31		-====Cloud Template R6 - Double Lane====
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"]]
34		-
35		-== **WS-Security on the 3rd generation runtime** ~*~* ==
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. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
38		-
39		-== **State Generation ~*~* ==
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.
42		-
43		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
44		-
45		-== **Feedback items ** ==
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.
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.
52		-
53		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
54		-
55		-== **Bug fixes ** ==
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"]]
	33	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
72	72
73	73	== **Key takeaways** ==
74	74
...	...	@@ -89,6 +89,6 @@
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.
	54	+~*~* Indicates a next-generation-architecture only feature.
93	93	{{/info}})))((({{toc/}}))){{/container}}
94	94	{{/container}}