Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+208 - Controlled State

Author

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

Content

...	...	@@ -2,48 +2,49 @@
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!** ... .
6	6
7		-== **Deployment Plan** ==
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
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	+== **State Generation~*~*** ==
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	+//__New Page__//
	12	+The following page has been added:
	13	+* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
14	14
	15	+Added support for ... .
15	15
16		-
17		-
18		-== **Store Improvements** ==
19		-
	17	+{{info}}The components are ... .{{/info}}
20	20
	19	+== **Metrics Storage Duration** ==
	20	+We will ... .
	21	+
21	21	== **Feedback Items** ==
22	22
23		-//__Alerting manual pause__//
24		-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.
	24	+//__Import from store__//
	25	+The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
25	25
26		-//__Ordering of graphs in Manage__//
27		-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).
28		-
29		-
	27	+//__Import from store__//
	28	+The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
	29	+
30	30	== **Bug Fixes** ==
31	31
32		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
33		-In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	32	+//__Topic and event-processor names__//
	33	+The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
34	34
35		-//__Ensure that differing container configurations deploy the correct configuration__//
36		-When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	35	+//__Topic and event-processor names__//
	36	+The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
37	37
38		-//__Remove queurying options in Manage__//
39		-To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
40		-
41	41	== **Fancy Forum Answers** ==
42	42
43	43	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:
44	44
45		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	42	+* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
	43	+* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
	44	+* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
	45	+* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
46	46
	47	+
47	47	== **Key takeaways** ==
48	48
49	49	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: