Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+213 - Joyful Journeys

Content

...	...	@@ -1,50 +1,83 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
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.
	6	+**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
6	6
7		-== **Deployment Plan** ==
	8	+== **Pop-up Improvements** ==
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	+//__Property releases__//
	11	+When a new property release is created, this property release can now be viewed and deleted.
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.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14	14
	15	+//__Runtime deletion__//
	16	+When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
15	15
16		-
17		-
18		-== **Store Improvements** ==
19		-
	18	+//__Wiretap & debug error messages__//
	19	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
20	20
	21	+//__Action messages__//
	22	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
	23	+
	24	+== **Formatting & Alignments** ==
	25	+
	26	+//__Input fields__//
	27	+Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
	28	+
	29	+//__UI improvements__//
	30	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
	31	+
	32	+//__Component changes reversion__//
	33	+In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
	34	+
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
	37	+
	38	+//__Queue browser timestamps__//
	39	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
	40	+
	41	+//__Addition and deletion of internal recipients__//
	42	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
	43	+
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.
	46	+//__Update flows__//
	47	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
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).
	49	+//__Q&A forum search__//
	50	+The option to search by pressing the Enter key has been added to the Q&A forum.
28	28
	52	+//__Memory settings__//
	53	+It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
29	29
	55	+//__Runtime validation__//
	56	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	57	+
	58	+//__Runtime overview image versions__//
	59	+Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
	60	+
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.
	63	+//__Removal of onramp__//
	64	+We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
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.
	66	+//__Runtime statistics details__//
	67	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
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.
	69	+//__Deployment prechecks__//
	70	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
40	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"]]
	76	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	77	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	78	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
46	46
47		-== **Key takeaways** ==
	80	+== **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:
50	50
...	...	@@ -55,7 +55,6 @@
55	55	* Check out the release notes [here]
56	56	* Start thinking about how the license tracker can aid your development
57	57	* Start thinking about major, minor, and patch
58		-* Upgrade to the latest build number
59	59	* Keep making great integrations
60	60
61	61	Let's stay in touch and till next time!
...	...	@@ -63,6 +63,11 @@
63	63	{{info}}
64	64	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65	65
66		-~*~* Indicates a next-generation-architecture only feature.
67		-{{/info}})))((({{toc/}}))){{/container}}
	98	+{{/info}}
	99	+)))
	100	+
	101	+(((
	102	+{{toc/}}
	103	+)))
68	68	{{/container}}
	105	+{{/container}}