Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,116 +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 had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger 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		-== **Dynamic Alerts** ~*~* ==
	8	+== **Pop-up Improvements** ==
8	8
9		-{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
	10	+//__Property releases__//
	11	+When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
10	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
12	12
13		-We offer alerting on five types.
	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		-* Error message
16		-* Log message
17		-* Queue consumers
18		-* Messages in queue
19		-* Queue throughput
	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.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.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.
22	22
23		-These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
	24	+== **Formatting & Alignments** ==
24	24
25		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
	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.
26	26
27		-Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
	29	+//__UI improvements__//
	30	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
28	28
29		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
	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.
30	30
31		-== **Debugger ** ~*~* ~* ==
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
32	32
33		-{{warning}}Note that this functionality only works when the following criteria are met.
34		-* Your JMS server is running on the 3rd generation runtime
35		-* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36		-* The beta image is activated
37		-* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
	38	+//__Queue browser timestamps__//
	39	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
38	38
39		-As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
	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.
40	40
41		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
	44	+== **Feedback Items** ==
42	42
43		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
	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.
44	44
45		-Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
	49	+//__Q&A forum search__//
	50	+The option to search by pressing the Enter key has been added to the Q&A forum.
46	46
47		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
	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.
48	48
49		-{{info}}Note the following limitations when working with the debugger.
50		- * Your entire model needs to be migrated to the 3rd generation runtime
51		- * Only **one** flow **per** runtime can be debugged **per** environment
52		- * There is only **one** overview in which **all** debugged messages are shown
53		- * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54		- * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55		- ** After five minutes the debug functionality will be shutdown automatically under water.
56		- ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
	55	+//__Runtime validation__//
	56	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
57	57
58		-== **Volume mapping - Network Share** ==
	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.
59	59
60		-This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
	61	+== **Bug Fixes** ==
61	61
62		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
	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).
63	63
64		-[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
	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.
65	65
66		-== **Feedback items ** ==
	69	+//__Deployment prechecks__//
	70	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
67	67
68		-We have also solved other feedback items besides the flow designer's critical updates.
69		-
70		-//__Improved validation feedback on non-supported WSS4J interceptor __//
71		-We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
72		-
73		-//__Improve help text in flow testing on Java classes__//
74		-We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
75		-
76		-//__Improved readibility of notification when trying to delete a runtime__//
77		-When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
78		-
79		-== **Bug fixes ** ==
80		-
81		-//__Keep selection when copying properties__//
82		-We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
83		-
84		-//__Check on security header improved for API Gateway__//
85		-We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
86		-
87		-//__Copy and paste default support objects__//
88		-With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
89		-
90		-//__Fix editability of properties when importing store items__//
91		-With this release, you can once again change property names upon importing a store item.
92		-
93	93	== **Fancy Forum Answers** ==
94	94
95	95	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:
96	96
97		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||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"]]
101	101
102		-== **Key takeaways** ==
	80	+== **Key Takeaways** ==
103	103
104		-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:
105	105
106	106	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
107	107	* If you have feedback or ideas for us, talk to the Platypus
108		-* 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.
109	109	* Clear your browser cache (Ctrl + Shift + Del)
110	110	* Check out the release notes [here]
111	111	* Start thinking about how the license tracker can aid your development
112	112	* Start thinking about major, minor, and patch
113		-* Upgrade to the latest build number
114	114	* Keep making great integrations
115	115
116	116	Let's stay in touch and till next time!
...	...	@@ -118,6 +118,11 @@
118	118	{{info}}
119	119	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
120	120
121		-~*~* Indicates a GEN3-only feature.
122		-{{/info}})))((({{toc/}}))){{/container}}
	98	+{{/info}}
	99	+)))
	100	+
	101	+(((
	102	+{{toc/}}
	103	+)))
123	123	{{/container}}
	105	+{{/container}}