Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-210 - Deployment Delights
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -2,63 +2,97 @@
2	2	{{container layoutStyle="columns"}}
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
	5	+
	6	+**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
5	5
6		-**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
	8	+== ** Announcement - TLS versions deprecated** ==
7	7
8		-== **Alerts** ==
	10	+Placeholder for info from Bas
9	9
10		-//__Topic approaching max size alert__//
11		-The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
	12	+{{info}}Text{{/info}}
12	12
13		-//__Missing metrics alert__//
14		-We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	14	+== **Announcement - Spring 6** ==
15	15
	16	+Placeholder for info from Jelle
	17	+
	18	+{{warning}}Text{{/warning}}
	19	+
	20	+== ** Updated release functionality - Infra flow selection** ==
	21	+
	22	+This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
	23	+
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	25	+
	26	+When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
	27	+
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	29	+
	30	+On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
	31	+
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	33	+
	34	+== ** Updated deploy functionality on-premise - Multiple environments selection** ==
	35	+
	36	+{{warning}}The following is only applicable under the following conditions:
	37	+ * Windows 2022 server
	38	+ * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
	39	+
	40	+When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
	41	+
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	43	+
16	16	== **Feedback Items** ==
	45	+//__Easier component selection in flow designer__//
	46	+The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
17	17
18		-//__Improved release build process__//
19		-When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
	48	+//__Improved handling of optionality in JSON on lists__//
	49	+Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
20	20
21		-//__Container version overview__//
22		-Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
	51	+//__Loading bar when searching for log entries__//
	52	+To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	54	+//__Improved feedback when deleting elements from Capture__//
	55	+To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes.
25	25
26		-//__Improved deployment process__//
27		-The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
	57	+//__Enhanced filter options in Manage__//
	58	+With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
28	28
29		-//__Rebuilding of images__//
30		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
	60	+//__Copy property names from Create__//
	61	+This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
31	31
32		-== **Bug Fixes** ==
	63	+//__Improved feedback during migration to the current-runtime architecture__//
	64	+We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
33	33
34		-//__Runtime metrics processing__//
35		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	66	+//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
	67	+We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
36	36
37		-//__Deployment plan__//
38		-We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
	69	+//__Cron trigger validation__//
	70	+We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
39	39
40		-//__View all store items__//
41		-An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
	72	+== **Bug Fixes** ==
	73	+//__Queue name validation__//
	74	+The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
42	42
43		-//__Out of memory behavior__//
44		-We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	76	+[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
45	45
46		-//__Max fetch size__//
47		-In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	78	+//__Removal of onramp__//
	79	+An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
48	48
	81	+//__eMagiz login__//
	82	+In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
	83	+
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54		-* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55		-* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56		-* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57		-* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
	88	+* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
	89	+* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
	90	+* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
	91	+* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
	92	+* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
58	58
	94	+== **Key Takeaways** ==
59	59
60		-== **Key takeaways** ==
61		-
62	62	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:
63	63
64	64	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -68,7 +68,6 @@
68	68	* Check out the release notes [here]
69	69	* Start thinking about how the license tracker can aid your development
70	70	* Start thinking about major, minor, and patch
71		-* Upgrade to the latest build number
72	72	* Keep making great integrations
73	73
74	74	Let's stay in touch and till next time!
...	...	@@ -76,7 +76,6 @@
76	76	{{info}}
77	77	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78
79		-~*~* Indicates a next-generation-architecture only feature.
80	80	{{/info}}
81	81	)))
82	82