Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-193 - Fan Out
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,83 +1,93 @@
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!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
6	6
7		-== **REST XML for API Gateway** ~*~* ==
	8	+== **Pop-up Improvements** ==
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	+//__Property releases__//
	11	+When a new property release is created, this property release can now be viewed and deleted.
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-blog-213-joyful-journeys-property-release.png]]
12	12
13		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
	15	+//__Runtime deletion__//
	16	+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.
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	+//__Wiretap & debug error messages__//
	19	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
	21	+//__Action messages__//
	22	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
18	18
19		-==**Cloud Template R23 - Single Lane** ==
	24	+== **Formatting & Alignments** ==
20	20
21		-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	+//__Input fields__//
	27	+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.
22	22
23		-==**Cloud Template R6 - Single Lane** ==
	29	+//__UI improvements__//
	30	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
24	24
25		-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"]]
	32	+//__Component changes reversion__//
	33	+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.
26	26
27		-==**Cloud Template R6 - Double Lane** ==
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
28	28
29		-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	+//__Queue browser timestamps__//
	39	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
30	30
31		-== **WS-Security on the 3rd generation runtime** ~*~* ==
	41	+//__Addition and deletion of internal recipients__//
	42	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
32	32
33		-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.
	44	+== **Feedback Items** ==
34	34
35		-== **State Generation ~*~* ==
	46	+//__Update flows__//
	47	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
36	36
37		-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.
	49	+//__Q&A forum search__//
	50	+The option to search by pressing the Enter key has been added to the Q&A forum.
38	38
39		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
	52	+//__Memory settings__//
	53	+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.
40	40
41		-== **Feedback items ** ==
	55	+//__Runtime validation__//
	56	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
42	42
43		-//__Removed OData as option for an API Gateway operation__//
44		-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	+//__Runtime overview image versions__//
	59	+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.
45	45
46		-//__Changes in API Gateway operation paths is automatically updated in Create__//
47		-When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
	61	+== **Bug Fixes** ==
48	48
49		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
	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).
50	50
51		-== **Bug fixes ** ==
	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.
52	52
53		-//__Prevent endless loop in Deploy -> User Management__//
54		-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.
	69	+//__Deployment prechecks__//
	70	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
55	55
56		-{{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}}
57		-
58		-//__Update error handling during migration to the 3rd generation runtime__//
59		-As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
60		-
61	61	== **Fancy Forum Answers** ==
62	62
63	63	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:
64	64
65		-* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
66		-* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
67		-* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
	76	+* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
	77	+* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
	78	+* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
68	68
69		-== **Key takeaways** ==
	80	+== **Key Takeaways** ==
70	70
71		-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:
	82	+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:
72	72
73	73	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74	* If you have feedback or ideas for us, talk to the Platypus
75		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	86	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76	76	* Clear your browser cache (Ctrl + Shift + Del)
77	77	* Check out the release notes [here]
78	78	* Start thinking about how the license tracker can aid your development
79	79	* Start thinking about major, minor, and patch
80		-* Upgrade to the latest build number
81	81	* Keep making great integrations
82	82
83	83	Let's stay in touch and till next time!
...	...	@@ -85,6 +85,11 @@
85	85	{{info}}
86	86	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87	87
88		-~*~* Indicates a GEN3-only feature.
89		-{{/info}})))((({{toc/}}))){{/container}}
	98	+{{/info}}
	99	+)))
	100	+
	101	+(((
	102	+{{toc/}}
	103	+)))
90	90	{{/container}}
	105	+{{/container}}