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	+203 - Fast Paced

Author

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

Content

...	...	@@ -2,104 +2,40 @@
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 processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
6	6
7		-== **Deployment Plan** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
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.
11		-
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
14		-
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
17		-
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
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.
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.
26		-
27		-== **Store Improvements** ==
28		-
29		-//__Message definition elements order__//
30		-We fixed an issue that the order of message definition elements was changed after being imported.
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.
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.
37		-
38	38	== **Feedback Items** ==
39	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.
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
42	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).
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
45	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		-//__SOAP Web services path__//
74		-Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
75		-
76	76	== **Bug Fixes** ==
77	77
78		-//__Flow designer styling__//
79		-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.
	20	+//__Ensure no flow can be in a release twice__//
	21	+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.
80	80
81		-//__Partial search for messages__//
82		-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".
	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.
83	83
84		-//__Disk usage after cloud template update__//
85		-In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
86		-
87		-//__Error handling migration__//
88		-If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
89		-
90	90	== **Fancy Forum Answers** ==
91	91
92	92	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:
93	93
94		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
95	95
96	96	== **Key takeaways** ==
97	97
98		-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:
	34	+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:
99	99
100	100	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
101	101	* If you have feedback or ideas for us, talk to the Platypus
102		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	38	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
103	103	* Clear your browser cache (Ctrl + Shift + Del)
104	104	* Check out the release notes [here]
105	105	* Start thinking about how the license tracker can aid your development