Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+211 - Log Luminary

Author

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

Content

...	...	@@ -1,65 +1,82 @@
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 few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Announcement - Release Properties** ==
8		-As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	8	+== **Overviews and logging** ==
	9	+//__Runtime overview__//
	10	+We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
9	9
10		-== ** Deploy Architecture - Apply To Environment improvements ** ==
11		-As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
	12	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
12	12
13		-//__Enhanced right-hand view within Deployment Plan context__//
14		-When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	14	+//__Missing properties overview__//
	15	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
15	15
16		-{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
	17	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
17	17
18		-//__Improved timeout settings when deploying__//
19		-To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	19	+//__Runtime restart or redeploy overview__//
	20	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
20	20
21		-{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	22	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
22	22
23		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
24		-To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
	24	+//__Missing log entries__//
	25	+We improved crash handling so that log messages clearly show when and why a container failed to start.
25	25
26		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	27	+//__Runtime logging__//
	28	+We fixed a bug where no new log messages were showing up, even though they were produced by the container.
27	27
28		-//__Improved loading speed of Manage Dashboard__//
29		-This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	30	+== **Feedback Items** ==
30	30
31		-== **Store Improvements** ==
32	32
33		-//__Importing in Design is improved__//
34		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
	33	+//__Breaking changes pop-up__//
	34	+Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
35	35
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
	37	+
	38	+//__External recipients emailaddress__//
	39	+The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
	40	+
	41	+//__Broker queue metrics dashboards__//
	42	+It is now possible to select the MQTT broker in the queue metrics dashboards.
	43	+
	44	+//__Runtime image version__//
	45	+The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
	46	+
	47	+
36	36	== **Bug Fixes** ==
37	37
38		-//__Deprecated reminder pop-up removed__//
39		-We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	50	+//__Message throughput__//
	51	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
40	40
41		-//__Improved selection area in Flow Designer__//
42		-When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
	53	+//__Cloud template upgrade unjust rollback__//
	54	+An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
43	43
44		-//__Improved Kafka settings__//
45		-For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	56	+//__Next generation block__//
	57	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
46	46
47		-{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
	59	+//__Deployment execution error message__//
	60	+In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
48	48
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
	66	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	67	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	68	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	69	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	70	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
55	55
	72	+
56	56	== **Key takeaways** ==
57	57
58		-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:
	75	+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:
59	59
60	60	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61	* If you have feedback or ideas for us, talk to the Platypus
62		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	79	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63	63	* Clear your browser cache (Ctrl + Shift + Del)
64	64	* Check out the release notes [here]
65	65	* Start thinking about how the license tracker can aid your development
...	...	@@ -72,6 +72,12 @@
72	72	{{info}}
73	73	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74
75		-~*~* Indicates a GEN3-only feature.
76		-{{/info}})))((({{toc/}}))){{/container}}
	92	+~*~* Indicates a next-generation-architecture only feature.
	93	+{{/info}}
	94	+)))
	95	+
	96	+(((
	97	+{{toc/}}
	98	+)))
77	77	{{/container}}
	100	+{{/container}}