Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+201 - Be Informed

Author

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

Content

...	...	@@ -2,98 +2,64 @@
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 few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
	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	6
7		-== **Deployment Plan** ==
	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	8
9		-//__Improved deployment plan to make the process better and more predictable__//
10		-The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
	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.
11	11
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
	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	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	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	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	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.
20	20
21		-//__Cleanup old images__//
22		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	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}}
23	23
24		-//__Performance improvements for loading releases__//
25		-Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
	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.
26	26
27		-== **Store Improvements** ==
	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}}
28	28
29		-//__Message definition elements order__//
30		-We fixed an issue that the order of message definition elements was changed after being imported.
	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.
31	31
32		-//__Improting a store item with synchronous message definitions__//
33		-We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
	31	+== **Store Improvements** ==
34	34
35		-//__Importing store items containing static copies__//
36		-We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
	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.
37	37
38		-== **Feedback Items** ==
39		-
40		-//__Alerting manual pause__//
41		-A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
42		-
43		-//__Ordering of graphs in Manage__//
44		-The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
45		-
46		-//__UTC times in Grafana panels__//
47		-All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
48		-
49		-//__Update flow designer version__//
50		-The framework used in the flow designer has been updated to the latest version.
51		-
52		-//__Carwash track TLS versions in logging__//
53		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
54		-
55		-//__Moving channels in the flow designer__//
56		-Moving already attached channels in the flow designer has been made sligthly easier.
57		-
58		-//__Topic sizes description change__//
59		-In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
60		-
61		-//__Password change notification__//
62		-When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
63		-
64		-//__Password comparison__//
65		-When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
66		-
67		-//__Inactive user alerting__//
68		-Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
69		-
70		-//__Alphabetical sorting on user level in HTTP statistics__//
71		-Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
72		-
73	73	== **Bug Fixes** ==
74	74
75		-//__Flow designer styling__//
76		-The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
	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.
77	77
78		-//__Partial search for messages__//
79		-It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
	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.
80	80
81		-//__Disk usage after cloud template update__//
82		-Several accounts showed significantly more disk usage after the last cloud template update, this has been resolved.
	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.
83	83
	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}}
	48	+
84	84	== **Fancy Forum Answers** ==
85	85
86	86	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:
87	87
88		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	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"]]
89	89
90	90	== **Key takeaways** ==
91	91
92		-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:
	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:
93	93
94	94	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95	95	* If you have feedback or ideas for us, talk to the Platypus
96		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	62	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
97	97	* Clear your browser cache (Ctrl + Shift + Del)
98	98	* Check out the release notes [here]
99	99	* Start thinking about how the license tracker can aid your development
...	...	@@ -106,6 +106,6 @@
106	106	{{info}}
107	107	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
108	108
109		-~*~* Indicates a next-generation-architecture only feature.
	75	+~*~* Indicates a GEN3-only feature.
110	110	{{/info}})))((({{toc/}}))){{/container}}
111	111	{{/container}}