Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-185 - Get ready
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -1,69 +1,119 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[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.
4	4
5		-**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
	8	+== ** Announcement - TLS versions deprecated** ==
6	6
7		-==**Store additions**==
8		-We have released several Store items that can be used in the Design Store and which include complete data models and transformations. See the list below of the components that have these.
9		-
10		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 3.png]]
	10	+Placeholder for info from Bas
11	11
12		-==**Audit trail User Management**==
13		-Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
14		-
15		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
	12	+{{info}}Text{{/info}}
16	16
17		-==**Next Generation Monitoring & Alerting engine** (-*-*)==
18		-In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
19		-
20		-* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
21		-* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
22		-* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
23		-* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
24		-* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
25		-
26		-
27		-=== **Improvements** ===
28		-
29		-* Performance Deployment plan
30		-When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
31		-
32		-* Flow Designer updates
33		-We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
34		-
35		-[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
36		-
37		-* Store
38		-We have fixed several smaller Store import issues to improve the user experience.
39		-
	14	+== **Announcement - Spring 6** ==
	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	+
	44	+== **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.
	47	+
	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.
	50	+
	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.
	53	+
	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.
	56	+
	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.
	59	+
	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.
	62	+
	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.
	65	+
	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.
	68	+
	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.
	71	+
	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.
	75	+
	76	+[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
	77	+
	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.
	80	+
	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	+
40	40	== **Fancy Forum Answers** ==
41	41
42		-As always, a gentle reminder to all 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:
	86	+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:
43	43
44		-* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
45		-* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||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"]]
46	46
47		-== **Key takeaways** ==
	94	+== **Key Takeaways** ==
48	48
49		-Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	96	+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
51	51	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
52	52	* If you have feedback or ideas for us, talk to the Platypus
53		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	100	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54	54	* Clear your browser cache (Ctrl + Shift + Del)
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		-* Check out the new documentation portal.
61	61
62	62	Let's stay in touch and till next time!
63	63
64	64	{{info}}
65		-~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	110	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66	66
67		-~*~* Indicates a GEN3-only feature.
68		-{{/info}})))((({{toc/}}))){{/container}}
	112	+{{/info}}
	113	+)))
	114	+
	115	+(((
	116	+{{toc/}}
	117	+)))
69	69	{{/container}}
	119	+{{/container}}