Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+206 - Situational Deployment

Content

...	...	@@ -1,49 +1,50 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
	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.
7	7
8		-== **Feedback Items** ==
9		-//__Cron triggers__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
	7	+== **Deployment Plan** ==
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	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.
13	13
14		-//__Design changes__//
15		-If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
18	18
19		-== **Bug Fixes** ==
20		-//__Trigger activation__//
21		-Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
	16	+
	17	+
	18	+== **Store Improvements** ==
	19	+
22	22
23		-//__Multiple users deploying__//
24		-Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
	21	+== **Feedback Items** ==
25	25
26		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	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.
27	27
28		-//__Invalid memory configurations__//
29		-We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
	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).
30	30
31		-//__Property value synchronization__//
32		-Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33	33
34		-//__JMS number__//
35		-The number on the JMS container correctly displays the amount of queues present in Design.
	30	+== **Bug Fixes** ==
36	36
37		-[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
	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.
38	38
	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.
	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	+
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
43		-* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44		-* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
	45	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
45	45
46		-== **Key Takeaways** ==
	47	+== **Key takeaways** ==
47	47
48	48	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:
49	49
...	...	@@ -51,9 +51,10 @@
51	51	* If you have feedback or ideas for us, talk to the Platypus
52	52	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53	53	* Clear your browser cache (Ctrl + Shift + Del)
54		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
	55	+* Check out the release notes [here]
55	55	* Start thinking about how the license tracker can aid your development
56	56	* Start thinking about major, minor, and patch
	58	+* Upgrade to the latest build number
57	57	* Keep making great integrations
58	58
59	59	Let's stay in touch and till next time!
...	...	@@ -61,11 +61,6 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
64		-{{/info}}
65		-)))
66		-
67		-(((
68		-{{toc/}}
69		-)))
	66	+~*~* Indicates a next-generation-architecture only feature.
	67	+{{/info}})))((({{toc/}}))){{/container}}
70	70	{{/container}}
71		-{{/container}}