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	+202 - New Equilibrium

Author

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

Content

...	...	@@ -2,104 +2,73 @@
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 crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **Deployment Plan** ==
	7	+== **Release Properties** ==
	8	+As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
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	+* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
	11	+* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
	12	+* When adding or editing a property, you can **now** select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
	13	+* A, for most, new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
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.
	15	+{{info}}For more information, please check out the following microlearnings:
14	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	17	+* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	18	+* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
	19	+* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
17	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	21	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	22	+{{/info}}
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.
	24	+== ** Manage - Graphs improvements ~*~* ** ==
	25	+As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
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.
	27	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
26	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.
	31	+//__Improved editability when testing in eMagiz without Edit rights in Create__//
	32	+Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
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).
	34	+//__Improved auditability on Deploy Architecture__//
	35	+To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
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.
	37	+//__Test your own exported store content__//
	38	+We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
48	48
49		-//__Update flow designer version__//
50		-The framework used in the flow designer has been updated to the latest version.
	40	+{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
51	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.
	42	+//__Improved comparison of flows in the releases overview__//
	43	+We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
54	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.
	47	+//__Improved validation on XPath header enricher__//
	48	+To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
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".
	50	+//__Cancel behavior on flow testing property overview fixed__//
	51	+We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
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.
	53	+//__Cancel behavior on flow fragment level when exporting store content__//
	54	+We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
86	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.
	56	+//__Adding numbers on containers in Deploy Architecture__//
	57	+With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
89	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"]]
	63	+* [[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:
	67	+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.
	71	+* 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