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	+189 - Private Eye

Author

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

Content

...	...	@@ -2,84 +2,81 @@
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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
6	6
7		-== **Deployment Plan** ==
	7	+== **Private Store** ==
	8	+On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
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	+{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
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.
	12	+== **3rd generation runtime bolstering** ==
14	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	14	+This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
17	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	16	+//__SOAP and REST web services migration, including splitting them__//
	17	+With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
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.
	19	+//__Changing SSL settings for 3rd generation runtime models works__//
	20	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
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.
	22	+//__Improved migration for JMS flows__//
	23	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
26	26
27		-== **Store Improvements** ==
	25	+{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
28	28
29		-//__Message definition elements order__//
30		-We fixed an issue that the orders of message definition’s elements were changed after they were imported.
	27	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	28	+As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
31	31
32		-//__Message definition elements order__//
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.
	30	+//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
	31	+We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
34	34
35		-== **Feedback Items** ==
	33	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	34	+With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
36	36
37		-//__Alerting manual pause__//
38		-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.
	36	+//__Added "Reset" functionality__//
	37	+With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
39	39
40		-//__Ordering of graphs in Manage__//
41		-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).
	39	+== **Feedback items ** ==
42	42
43		-//__UTC times in Grafana panels__//
44		-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.
	41	+We have also solved other feedback items besides the flow designer's critical updates.
45	45
46		-//__Update flow designer version__//
47		-The framework used in the flow designer has been updated to the latest version.
	43	+//__Improved naming convention on Store related pages__//
	44	+We have improved various display names using the merge functionality within our store offering.
48	48
49		-//__Carwash track TLS versions in logging__//
50		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
	46	+//__Update security protocols for our internal architecture__//
	47	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
51	51
52		-//__Moving channels in the flow designer__//
53		-Moving already attached channels in the flow designer has been made sligthly easier.
	49	+//__Improved read-only description for "if exists" constructions in Transformations__//
	50	+To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
54	54
55		-//__Topic sizes description change__//
56		-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.
57	57
58		-//__Password change notification__//
59		-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.
	53	+== **Bug fixes ** ==
60	60
61		-//__Password comparison__//
62		-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.
	55	+//__Decent validation feedback when not filling in the property value__//
	56	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
63	63
	58	+//__Incorrect resource locations__//
	59	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
64	64
65		-== **Bug Fixes** ==
	61	+//__Apply to environment in User Management performance improvement__//
	62	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
66	66
67		-//__Flow designer styling__//
68		-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.
69		-
70	70	== **Fancy Forum Answers** ==
71	71
72	72	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:
73	73
74		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	68	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	69	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	70	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	71	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
75	75
76	76	== **Key takeaways** ==
77	77
78		-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:
	75	+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:
79	79
80	80	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81	81	* If you have feedback or ideas for us, talk to the Platypus
82		-* 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.
83	83	* Clear your browser cache (Ctrl + Shift + Del)
84	84	* Check out the release notes [here]
85	85	* Start thinking about how the license tracker can aid your development
...	...	@@ -92,6 +92,6 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a next-generation-architecture only feature.
	92	+~*~* Indicates a GEN3-only feature.
96	96	{{/info}})))((({{toc/}}))){{/container}}
97	97	{{/container}}