Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+188 - Close Encounters

Author

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

Content

...	...	@@ -2,98 +2,72 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.
6	6
7		-== **Deployment Plan** ==
	7	+== **Store - Next phase** ==
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.
	9	+This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
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.
	11	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
14	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	13	+{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
17	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	15	+== **New eMagiz Mendix Connector** ==
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.
	17	+This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
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.
	19	+{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
26	26
27		-== **Store Improvements** ==
	21	+== **Flow version restore** ~* ==
28	28
29		-//__Message definition elements order__//
30		-We fixed an issue that the order of message definition elements was changed after being imported.
	23	+On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
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.
	25	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
34	34
35		-//__Importing store itmes containing static copies__//
36		-We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
	27	+{{warning}}Note that the following restrictions apply when restoring to a previous version:
	28	+ * Changes made on definition and transformation level are **not** restored
	29	+ * You will **not** be able to restore to any flow version that was created before October 17th, 2022
	30	+ * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
	31	+ * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
37	37
38		-== **Feedback Items** ==
	33	+== **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.
	35	+We have also solved other feedback items besides the flow designer's critical updates.
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).
	37	+//__Improved help texts Kafka component__//
	38	+The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
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.
	40	+//__Improved warning message when Message redelivery cannot be adequately executed__//
	41	+We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
48	48
49		-//__Update flow designer version__//
50		-The framework used in the flow designer has been updated to the latest version.
	43	+//__See Flow Designer errors on the Create overview__//
	44	+To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
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.
	46	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
54	54
55		-//__Moving channels in the flow designer__//
56		-Moving already attached channels in the flow designer has been made sligthly easier.
	48	+{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
57	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.
	52	+//__Update Swagger File when changing the order of entities in gateway message__//
	53	+In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
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".
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.
83		-
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"]]
	59	+* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
	60	+* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
	61	+* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
	62	+* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||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:
	66	+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.
	70	+* 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.
	83	+~*~* Indicates a GEN3-only feature.
110	110	{{/info}})))((({{toc/}}))){{/container}}
111	111	{{/container}}